Questions for Confluence license has expired.

Please purchase a new license to continue using Questions for Confluence.

Exalate does sometimes not properly reflect moving back tickets into the project with the connection. What can I do?

 
1
0
-1

Prerequisites:

We have to Jira instances, both should contain the same tickets (with same IDs) for shared projects. Lets call the Jira instances J1 & J2 the project with a exalate connection EXA and an internal project without the sync INT


Steps:

We have a ticket EXA-1 that is synced between J1 & J2


If now on J1 someone moves EXA-1 to project INT (and it gets INT-1) we stop updating EXA-1 on J2.


Now if someone on J1 moves INT-1 back to EXA it becomes a new ticket EXA-2 (at least with heavily different workflows & statuses) 


Problem 1:

BUT it will still be synced to J2 as EXA-1.


Problem 2:

This leads for the next new ticket to be:

EXA-2 on J2 synced with EXA-3 on J1, which makes it really awful to talk about ticket IDs with people seeing only J1 or J2.


What can we do to avoid/mitigate? (moving of tickets is needed to be able to move a bug to a change request etc.)

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Hi Johannes,

      The change of Issue ID is not being produced by Exalate, this is an expected behaviour of Jira. More information on moving issues here.


      I would highly recommend reaching to the Atlassian Community in order to investigate if there is a way to modify the Issue ID.

      Additionally, I do not know the specifics of what you are trying to achieve, but an option to avoid these ID modifications could be using Exalate to create a connection between EXA J1 and INT J1 for instance.

      Best,
      Ezequiel

        CommentAdd your comment...