Confluence has been updated to ver 6.15.9. In case of any troubles, please contact infra team.

Project Key change

 
1
0
-1
Hello, We have changed the key for one of the projects, and the remote issues still shows the old key in the Sync Status. Is there away to have the new key updated in the Sync Status in the remote system
    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Hi Ziad,


      As explained in the following documentation page: https://docs.idalko.com/exalate/x/so0rAQ


      Whenever a user changes something in an issue, Jira will notify Exalate about the change by generating an update event. If the issue is under an update it gets synchronized.
      However, changing the project key does not trigger such an event. To synchronize a key change, the issue under sync needs to be touched by modifying something or by adding a comment in order to synchronize that information change. 


      Thanks,


      André



      1. Ziad Qadora

        Hi André,


        Thank you for the response.   Do we have to update each issue in the project where they key is changes manually or is there a way to do it for all issues in the project in a mass update?

      2. André Leroy-Beaulieu Castro

        Hi Ziad,


        You can use a trigger to select all issues in that project and do a bulk exalate, if you don't want to change the actual information of the issues, you can add something in the incoming processor that looks like this:


        issue.customKeys."foo" = "bar"


        and then do the bulk exalate, this will update those issues with the value "bar" into the "foo" custom Key, which will accomplish the update of the issue without really changing any data from the issues.


        Thanks,


        André

      CommentAdd your comment...