-
Bug
-
Resolution: Support Request
-
Medium
-
None
-
5.5
In production environments configuration are changing, and it is really easy to end-up with cases like:
- the server name has changed - that's the App Title of jira
- URL of of the target JIRA can change, domain do change!
- serverID of can change, for example when two instances are merged or split.
- jira macro code can be missing the serverid (yes only servername) – observed it quite often.
If any 2 of the above are happening at the same time, you are ending up with lots of broken JIRA macros, ones that you cannot solve using KB article https://confluence.atlassian.com/pages/viewpage.action?pageId=590251843
In order to fix this for good JIRA needs few patches:
- Auto repair URL redirected AppLinks - a 301 response on an AppLink should auto-reconfigure the app link. HTTP 301 is a permanent redirect, not a temporary one.
- When encountering a jira link that is using an AppLink that is redirected, fixit. If possible this should be part of self-repair scheduled task.
- When encountering a jira-macro without server-id, add the server id to it
- When unable to repair AppLinks from JIRA Macro include the servername and serverid in the error message displayed on the UI.
- Allow people to have aliases for servernames, that's the only way to fix previous point without having to do search and replace at database level.
- mentioned in
-
Page No Confluence page found with the given URL.