Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-715

Jira for Outlook authorization process fails to complete

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      The process of connecting the Jira for Outlook add-on with a site fails without any errors when selecting a project. 

      Steps to Reproduce

      1. Go to Outlook (web) and install the Jira Cloud add-on
      2. On the Create issue tab, select a Jira site and a project
      3. When the message "Please re-authorize Jira to create requests using request type and reporter fields in Jira Service Management project" appears, click on Re-authorize

      Expected Results

      Once the authorization flow is completed, you should be able to select an Issue type and proceed to create an issue.

      Actual Results

      When the Re-authorize button is clicked and permissions are reviewed, nothing happens. The issue type dropdown remains grayed out and it's not possible to proceed with issue creation.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [API-715] Jira for Outlook authorization process fails to complete

            Pinned comments

            Pinned by Victor Romero

            Tarun Walia (Inactive) added a comment -

            We have prioritised this issue, ETA for resolution is 14th August 2024.

            Tarun Walia (Inactive) added a comment - We have prioritised this issue, ETA for resolution is 14th August 2024.

            Tarun Walia (Inactive) added a comment -

            We are rolling out the fix in phases and have currently deployed it to 50% of the traffic.

            Tarun Walia (Inactive) added a comment - We are rolling out the fix in phases and have currently deployed it to 50% of the traffic.

            Pinned by Samyak Mehta

            Samyak Mehta added a comment -

            The fix for this issue is fully rolled out and must now be available to all the users.

            Samyak Mehta added a comment - The fix for this issue is fully rolled out and must now be available to all the users.

            All comments

            Pinned by Samyak Mehta

            Samyak Mehta added a comment -

            The fix for this issue is fully rolled out and must now be available to all the users.

            Samyak Mehta added a comment - The fix for this issue is fully rolled out and must now be available to all the users.

            Ollie Bright added a comment -

            Can confirm this issue is now resolved for us. 

            Thank you.

            Ollie Bright added a comment - Can confirm this issue is now resolved for us.  Thank you.

            emmeram added a comment -

            It works! Thank you!

            emmeram added a comment - It works! Thank you!

            Tarun Walia (Inactive) added a comment -

            We are rolling out the fix in phases and have currently deployed it to 50% of the traffic.

            Tarun Walia (Inactive) added a comment - We are rolling out the fix in phases and have currently deployed it to 50% of the traffic.

            kai.kursten added a comment -

            I just tested it out and the error is gone for us. 😊 I just created a ticket through this AddIn. 👍

            kai.kursten added a comment - I just tested it out and the error is gone for us. 😊 I just created a ticket through this AddIn. 👍

            Pinned by Victor Romero

            Tarun Walia (Inactive) added a comment -

            We have prioritised this issue, ETA for resolution is 14th August 2024.

            Tarun Walia (Inactive) added a comment - We have prioritised this issue, ETA for resolution is 14th August 2024.

            Paul Treacy added a comment -

            My Organisation is also affected by this issue.

            Paul Treacy added a comment - My Organisation is also affected by this issue.

            Marco Dieckhoff added a comment -

            We have the same issue as well. I also opened a support ticket, and they confirmed that our problem matches this bug.

            Marco Dieckhoff added a comment - We have the same issue as well. I also opened a support ticket, and they confirmed that our problem matches this bug.

            Paul Shinn added a comment -

            My company is also affected by this issue, is there an expected ETA on resolving this?

            Paul Shinn added a comment - My company is also affected by this issue, is there an expected ETA on resolving this?

            Steven Schroeder added a comment - - edited

            As per Atlassian's Cloud Bug Fixing Policy, I must express my concern that the issue we are experiencing is being categorized as Low priority. According to the policy, Low priority issues are described as "typically smaller paper cuts such as cosmetic errors, or non-critical functionality not behaving as expected." The impact of the issue we are facing is significant and goes beyond cosmetic errors or non-critical functionality.

            The problem is affecting workflow and productivity, which I believe warrants a higher priority than what has been assigned. I would appreciate it if you could revisit the priority level of this issue and consider the broader impact it has on operations.

            Steven Schroeder added a comment - - edited As per Atlassian's Cloud Bug Fixing Policy , I must express my concern that the issue we are experiencing is being categorized as Low priority. According to the policy, Low priority issues are described as " typically smaller paper cuts such as cosmetic errors, or non-critical functionality not behaving as expected. " The impact of the issue we are facing is significant and goes beyond cosmetic errors or non-critical functionality. The problem is affecting workflow and productivity, which I believe warrants a higher priority than what has been assigned. I would appreciate it if you could revisit the priority level of this issue and consider the broader impact it has on operations.

              2b3e87da7d62 Tarun Walia (Inactive)
              vromero Victor Romero
              Affected customers:
              71 This affects my team
              Watchers:
              79 Start watching this issue

                Created:
                Updated:
                Resolved: