Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-67323

"Jira Issues" fails to render when Jira Server is linked with Confluence Cloud

      Issue Summary

      The Application links created with Jira Server & Confluence Cloud fails to render Jira issues & displays the error "Unable to get data due to an unexpected error". Upon Editing the macro, gives a user the chance to login & approve.

      Environment

      • Jira Server
      • Confluence Cloud
      • Application links

      Steps to Reproduce

      1. Deploy Jira Server instance.
      2. Make it publicly accessible
      3. Connect through Application link
      4. Create few test tickets on Server
      5. Mention them on a Confluence Page.

      Expected Results

      Regardless of the user roles, it should render even if they are not able to authenticate once.

      Actual Results

      Presently it renders only for site-admins on both instances and validates OAuth authentication.

      Notes

      The API gives below results

      {"errors":[{"context":null,"message":"Please authenticate with JIRA to view issue details","exceptionName":"com.atlassian.integration.jira.JiraAuthenticationRequiredException","authenticationUri":"https://changesrandhawa.atlassian.net/wiki/plugins/servlet/applinks/oauth/login-dance/authorize?applicationLinkID=xxxxxxx","applicationName":"Jira JIRA"}]}

      Workaround

      One can provide site-admin access temporarily to the users so that they can authenticate at least once and later revoke their access. This will render the Jira issues permanently for them.

            [CONFCLOUD-67323] "Jira Issues" fails to render when Jira Server is linked with Confluence Cloud

            Atlassian Update - October 12, 2021

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - October 12, 2021 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              srandhawa@atlassian.com Supreet (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: