Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-62850

Update Confluence Links In JIRA Automatically Based On The New Applink Configurations

XMLWordPrintable

    • 35
    • 24
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem Definition

      When moving JIRA and Confluence to a different environment, most of the time in order to test, links between the two instances break. The new environment has different URLs, which affects the issue link in JIRA and page links in Confluence as they rely on application link which has been defined earlier on the older environment.

      Suggested Resolution

      Confluence links in JIRA need to be updated as the new applink is created.

      Temporary Resolution

      This issue can be solved by taking the steps at Application Link Issue When Moving JIRA and Confluence for now.

            [JRASERVER-62850] Update Confluence Links In JIRA Automatically Based On The New Applink Configurations

            Yona Foundation added a comment -

            After migrating Jira and Confluence from server to cloud, I've now to manually click "resolve" all Jira issue references from Confluence pages. This is a terrible task that could be prevented by enhancing the migration.

            Yona Foundation added a comment - After migrating Jira and Confluence from server to cloud, I've now to manually click "resolve" all Jira issue references from Confluence pages. This is a terrible task that could be prevented by enhancing the migration.

            Reaz Abdul added a comment -

            When I tried the in the article, modified the XML file and replace new url but in Jira issue, it is showing page id rather than page title.

            https://company.com/pages/viewpage.action?pageId=14420544 instead of 

            https://company.com/display/SpaceKey/Page+Title

            Please let me know hoe to overcome this.

            Reaz Abdul added a comment - When I tried the in the article, modified the XML file and replace new url but in Jira issue, it is showing page id rather than page title. https://company.com/pages/viewpage.action?pageId=14420544  instead of  https://company.com/display/SpaceKey/Page+Title Please let me know hoe to overcome this.

            Dan Christensen Dall added a comment -

            Hi, 

            We migrated a running server instance to a running data center and now it is not possible to updated all the macros from the server manually, only some can be updated? Is there something we can do to be allowed to updated these links in Jira from Confluence?? 

            We even tried to insert the macros from fresh and delete the "old" macro from migration, but still this does not work? 

            We do not have the issue when linking to/from projects/spaces that were not migrated.

             

            Extra info:

            We migrated 31 projects and 15-20 confluences spaces into a bigger data center instance. App link was working on data center (and still is) therefor we have not removed and re-established the app link.

            Dan Christensen Dall added a comment - Hi,  We migrated a running server instance to a running data center and now it is not possible to updated all the macros from the server manually, only some can be updated? Is there something we can do to be allowed to updated these links in Jira from Confluence??  We even tried to insert the macros from fresh and delete the "old" macro from migration, but still this does not work?  We do not have the issue when linking to/from projects/spaces that were not migrated.   Extra info: We migrated 31 projects and 15-20 confluences spaces into a bigger data center instance. App link was working on data center (and still is) therefor we have not removed and re-established the app link.

            Roel Boiten added a comment -

            Same here, when migrating from cloud to server the difference in URL is quite large and cannot easily be resolved with xml edit.

            Roel Boiten added a comment - Same here, when migrating from cloud to server the difference in URL is quite large and cannot easily be resolved with xml edit.

            Valerii added a comment -

            Comment for notification. I have the same problem. 

            Valerii added a comment - Comment for notification. I have the same problem. 

            marlonguerios added a comment -

            Same problem here! Not nice!

            marlonguerios added a comment - Same problem here! Not nice!

            Derek Schaible added a comment -

            This took me by surprise. Shouldn't this be a core function of the migration tool? We used the migration tool only to learn afterward that all our links are broken.

            Derek Schaible added a comment - This took me by surprise. Shouldn't this be a core function of the migration tool? We used the migration tool only to learn afterward that all our links are broken.

            stephan71 added a comment -

            We also need this feature.

            stephan71 added a comment - We also need this feature.

            Ajit Pol added a comment -

            We are in the same boat as Kevin. I wish we had known about this beforehand so that we could have planned better.

            Ajit Pol added a comment - We are in the same boat as Kevin. I wish we had known about this beforehand so that we could have planned better.

            Kalvin Stubbs added a comment -

            We have recently migrated out JIRA Cloud instance to an In-House JIRA Server instance.  This was done to allow the running of the XRay app which was not available to JIRA Cloud.  Upon completion of the migration we found that the JIRA links in Confluence did not update to the new instance even though a successful application link was established between JIRA and Confluence.  We currently have 130+ pages in Confluence and on average 50 links to JIRA on each page.  As of now my only recourse seems to be to manually update each link to point to our new instance.  An Automated process would be beneficial. But even before that if we had know that we would have run into this issue (perhpas a warning in the migrating documentation) we would have looked at other plans. 

            Kalvin Stubbs added a comment - We have recently migrated out JIRA Cloud instance to an In-House JIRA Server instance.  This was done to allow the running of the XRay app which was not available to JIRA Cloud.  Upon completion of the migration we found that the JIRA links in Confluence did not update to the new instance even though a successful application link was established between JIRA and Confluence.  We currently have 130+ pages in Confluence and on average 50 links to JIRA on each page.  As of now my only recourse seems to be to manually update each link to point to our new instance.  An Automated process would be beneficial. But even before that if we had know that we would have run into this issue (perhpas a warning in the migrating documentation) we would have looked at other plans. 

              Unassigned Unassigned
              somidi Sam Omidi (Inactive)
              Votes:
              171 Vote for this issue
              Watchers:
              126 Start watching this issue

                Created:
                Updated: