Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-28249

Links of JIRA Issues in Confluence Workbox Notification do not get updated when JIRA base URL has changed

XMLWordPrintable

      Steps to reproduce:
      1. Install JIRA and Confluence and configure the base URL (with context path) for example to:
      2. Create an application link between Confluence and JIRA
      3. Create a new issue in JIRA and then comment on the issue
      4. With a successful application link integration, you'll received notification of the comment in Confluence Workbox
      5. Click on the notification and you'll be directed to the issue e.g. http://10.60.1.80:8525/jira/browse/TST-56118
      6. Change JIRA context path/base URL to http://10.60.1.80:8525/jira1
      7. Re-configure application link between Confluence and JIRA with the new base URL
      8. Add a new comment on the existing issue in JIRA
      9. With a successful application link integration, you'll received notification of the new comment in Confluence Workbox
      10. Click on the notification and you'll not be successfully redirected to the issue because it was trying to redirect you to http://10.60.1.80:8525/jira/browse/TST-56118. Noticed that the context path does not reflect the new context path which is supposed to be "jira1"
      11. Clicking on the previous JIRA issue notification in Confluence Workbox also will not redirect you to the correct link as it was still pointing to the old base URL

      My assumption was that this URL must have been stored somewhere in the database and updating the URL manually from the database would work as a workaround. I've checked on Confluence AO_9412A1_AONOTIFICATION table but JIRA notifications are not stored in an absolute path but instead like this:

      /browse/TST-56118
/browse/BB-870
/browse/NCLIS-358

      I then looked into Confluence BANDANA table for application link configuration (assuming that Confluence take the base URL from the configured application link) and it appears that the new JIRA base URLs (both Application URL & Display URL) are stored correctly in the database:

      bandanakey bandanavalue
      applinks.admin.781ddc6c-b497-38d7-8fc3-aad86127c262.display.url <string>http://10.60.1.80:8525/jira1</string>
      applinks.admin.781ddc6c-b497-38d7-8fc3-aad86127c262.rpc.url <string>http://10.60.1.80:8525/jira1</string>

      Where does this URL stored or taken from?

            [CONFSERVER-28249] Links of JIRA Issues in Confluence Workbox Notification do not get updated when JIRA base URL has changed

            AdrienA (Inactive) added a comment -

            Thanks for your help! It works well now.

            AdrienA (Inactive) added a comment - Thanks for your help! It works well now.

            AdrienA (Inactive) added a comment - - edited

            I've installed Workbox from branch issue/CONF-26782 into Confluence 5.2-SNAPSHOT and JIRA 5.2.11. After changing the port of JIRA, changing the base url in the JIRA Administration, changing the applink in Confluence (by clicking "Relocate"), I've checked the Workday notification. It was still using the old port. I even created a new issue in JIRA and commented on it, and it kept using the old port, which is really strange, as if a cache wasn't refreshed.

            Actually, when checking "In-App Notifications" in Confluence Admin, it was still displaying the old URL. The link "Modify Linked Applications" redirects me to Applinks, where the URL is right. http://awesomescreenshot.com/06d17t4v06

            Also, when starting Confluence after moving JIRA, it doesn't find the JIRA Crowd directory and there's no way to change the URL.

            We'll need you to help us testing, when you have time, sorry

            AdrienA (Inactive) added a comment - - edited I've installed Workbox from branch issue/ CONF-26782 into Confluence 5.2-SNAPSHOT and JIRA 5.2.11. After changing the port of JIRA, changing the base url in the JIRA Administration, changing the applink in Confluence (by clicking "Relocate"), I've checked the Workday notification. It was still using the old port. I even created a new issue in JIRA and commented on it, and it kept using the old port, which is really strange, as if a cache wasn't refreshed. Actually, when checking "In-App Notifications" in Confluence Admin, it was still displaying the old URL. The link "Modify Linked Applications" redirects me to Applinks, where the URL is right. http://awesomescreenshot.com/06d17t4v06 Also, when starting Confluence after moving JIRA, it doesn't find the JIRA Crowd directory and there's no way to change the URL. We'll need you to help us testing, when you have time, sorry

            edith (Inactive) added a comment -

            Hi Tim,

            Since your instance isn't integrated with JIRA, it sounds like you're affected by a different issue: CONF-26782. Both issues are similar, but the fix that is currently being reviewed for this ticket won't solve your problem (which arises when the base URL of Confluence is changed, rather than the display URL of the instance's application links) - so you may want to watch CONF-26782 instead.

            Sorry for the inconvenience!

            Regards,
            Edith

            edith (Inactive) added a comment - Hi Tim, Since your instance isn't integrated with JIRA, it sounds like you're affected by a different issue: CONF-26782 . Both issues are similar, but the fix that is currently being reviewed for this ticket won't solve your problem (which arises when the base URL of Confluence is changed, rather than the display URL of the instance's application links) - so you may want to watch CONF-26782 instead. Sorry for the inconvenience! Regards, Edith

            Tim Rosenberger added a comment -

            I'm using Confluence 5.1 only (no JIRA tie-in)and still running into this issue. Confluence is running solely as an internal knowledge base and project management tool for a very small group.
            I was assigned a new IP/URL by senior IT because we only had a few users, and communication about the new URL for login would not be unduly difficult. I had no idea it might have a detrimental effect on notifications.

            Tim Rosenberger added a comment - I'm using Confluence 5.1 only (no JIRA tie-in)and still running into this issue. Confluence is running solely as an internal knowledge base and project management tool for a very small group. I was assigned a new IP/URL by senior IT because we only had a few users, and communication about the new URL for login would not be unduly difficult. I had no idea it might have a detrimental effect on notifications.

              etom edith (Inactive)
              hsuhailah Hanis Suhailah (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 5m
                  5m