The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe

How to sync epics, stories and subtasks using a visual mode connection


As in summary, the challenge is 

  • Setup a Jira On Premise (A) to Jira On Premise (B) visual mode connection
  • ensure that stories are synced such that the epic relation is respected
    Ie. when Story-A1 is related to Epic-A1, then Story-B1 (the twin of Story-A1) is part of Epic-B1 (the twin epic of Epic-B1


    CommentAdd your comment...

    1 answer


      There are different levels to answer this question

      • First level is that the combination Epic, Story, Subtask is synced correctly
      • Second level is that the whole Epic, with all its stories, and subtasks are synced in one go
      • Third level is to have this functionality works bidirectionally
      • Fourth level is to have it on board level, including sprints and all that jazz

      This answer will focus on the first level:

      • Sync an epic correctly (epic name is mandatory)
      • Whenever a story is synced, ensure that the epic link is set correctly
      • Whenever a subtask is synced, ensure that the parent is set correctly

      All of this needs to work on a visual mode connection

      Assume now for a moment that you have setup a visual connection 'a' to 'b' (a and b are the short names which you define when setting up the conenction)

      Apart from configuring standard fields, you will have to define a script rule to ensure that the issue relations (Story to Epic, Subtask to parent) are being respected.

      As there is currently no graphical rule allowing to configure this behaviour. you will have to revert to the scripted rule

      And in the script enter the code as detailed here

      Some explanation

      • Line 1
        Apply the logic on side 'b' 
      • Line 3 and line 4
        if the incoming sync is an epic, ensure that the epic name is set correctly to the epic name on the source
      • Line 7
        Check if the incoming sync is about a subtask. It will be the case because the parentId is set.
        (psst - this is specific for jira-jira. ado-Jira is a bit different)

      • Line 10-12
        In case that the incoming sync is about a subtask, calculate the twin parent, and set it accordingly

      • Line 18-20
        In the case of a story, set the epic link

      There is a flaw in the example above, but we leave it as an exercise to the reader to locate the flaw in the logic. 
      Hint - what happens with issues not part of an epic.

      Next up - if time allows - we will focus on level 2 of the epic sync case

      1. Francis Martens (iDalko)

        There is some doubt that this configuration works.
        Therefore a video

        Note the examples are examples and not full implementations

      CommentAdd your comment...