-
Bug
-
Resolution: Fixed
-
High
-
38
-
Severity 3 - Minor
-
2
-
Issue Summary:
Broken links to Confluence pages are not visible in the new issue view. In the old issue view the error "wiki page failed to load" is displayed instead of the link.
Steps to Reproduce
1. Open an issue
2. Link a confluence page in old or new issue view
Expected Results:
Ideally, the confluence links should have been visible as expected in the old issue view and new issue view
Actual Results
In the new issue view, sometimes the confluence links are not visible at all, some other times they show an error message like the one in below screenshot:
In the old issue view, a "wiki page failed to load" ** error is displayed.
Workaround
Sometimes this issue is caused by some leftover Application Links pointing to an old Confluence site and it is enough to remove those application links by following the steps in: How to Remove Application Links via REST API
However, in cases where this doesn't work, you may want to Contact Support in order to have this issue addressed.
Further Investigations
We hypothesise that in many cases, the root cause of this issue is that (post-migration/import) there is a case of a duplicated Application Links for the same instance, where one of them is ‘broken’. These duplicate non-system App Links can be created even through the Jira UI.
In this case, we believe the System Application Link should be the one used to perform this integration with Confluence/Jira. We see problems arise when Jira Issues use the broken, duplicated App Link (in this example, the 'Confluence' App Link).
On a Jira Issue, when we try to link a Confluence page using the broken App Link, we receive the following authentication failure:
Additionally, when a broken App Link exists, the rendering of remote links in Issue View breaks:
But after deleting the broken App Link, the Issue View rendering of remote links is fixed:
Possible Long-Term Fix
- We have thoroughly checked our code, and there are no bugs on our side. We validate that the appId passed to us maps to an existing App Link (if it doesn't, we replace it from the request URL), however we have no way of determining if the App Link itself is 'faulty' or not.
After speaking with the App Links team (see this Slack thread), they informed us about 2 current projects due to be completed towards the end of March 2024:
- https://team.atlassian.com/project/ATLAS-46756/about (will resolve corruption issues, duplication issues and assorted sync issues)
- https://team.atlassian.com/project/ATLAS-54549/updates (will change system App Links to use ASAP, and will involve adding checks to prevent duplication)
We believe that the completion of the above projects (particularly the second one) may lead to the root cause of this JAC being resolved. We are still waiting for confirmation from the App Links team to confirm this.
- relates to
-
-
- Closed
-
-
MIG-98 Confluence links in Jira issues should be updated automatically based on the new applink configurations
- Closed
-
- Closed
- is action for
-
KEN-70 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-75182] Links to Confluence pages broken or not appearing on new and old issue view
Hi all,
This is Matthew from the Jira Cloud Applinks team.
Thank you for your patience as we work on a proper resolution to this issue. I’m pleased to say we have successfully implemented and tested a fix as part of a series of wider stability and robustness improvements to Application Links within Jira.
We are currently verifying the performance and stability of these new changes, and this work is ongoing. In order to deliver this safely, we have made the difficult decision to push back the release - we expect the fix to be in your hands by the end of September 2024 at the latest.
Thank you for your continued patience, and we hope to have good news soon.
Best,
Matthew
Hi everyone,
This is Behzad from the Jira Cloud AppLinks team. Thank you for your patience as we've worked on a fix for this bug. We have the fix ready for release, however, we are currently on pause to introduce some measures to reduce the risk of applying changes to production tenants. We know you have been waiting eagerly for this fix as we are, and we will resume the ability to release this fix as soon as we are sure that changes to your experience won't create a future product outage. Thank you again for your patience, and we hope to have some good news soon in July 2024.
Best,
Behzad
Hi everyone,
This is Behzad from the Jira AppLinks team. Thank you for your patience as we work on fixing this bug. We have identified the root cause for this bug, and we’re exploring solutions to address it. We expect the fix to be released by the end of June 2024. We will be providing any updates as they come. Thank you again for your patience!
Best,
Amirbehzad Eslami
Hi there, there's a number of support tickets linked here across the time it's been open. This issue is expected to be fixed in April with a series of significant AppLinks improvements rolled out at the same time. Moving it to "in progress" to reflect it's pending state to "Done" in April.
Hello support,
Bug identified, reproduced by support.
Now just handover to development team. Who is responsible for next step ?
what is next action to get moved from "Gathering interest" to "Short term backlog"
How many years to wait ??
Nothing more to add here. Bug is not a new feature to gather impact Votes.
| Gathering impact | This issue has been reviewed, but needs more supporting information to gauge the pervasiveness of the problem. |
Reproducing reminder:
Bug happenes for every issue adding new Confluence link 1st time
any Link search result is "We couldn't load this page. Open in Confluence"
PS. do not repeat the problem on same issue with same link you tried already.
For regular jira user it feels like basic functionality bug
"can not add wiki page to Jira issue Links section" ...
... confluence links broken ...
reported issue continues here as Bug ,
https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-594871
"We couldn't load this page. Open in Confluence" 3.result picture here
Hi all,
Thank you for your patience these past months.
This issue has now been resolved.
Kind Regards,
Matthew | Jira Applinks Team