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

Can confirm this issue is now resolved for us. 

Thank you.

It works! Thank you!

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

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

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

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

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

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.

This would really enhance our experience with Jira.  We will also open a ticket to gain traction on this request.

Also having same issue.

It seems to be mainly limited to "Create Issue" for service managment project. When adding to existing issues in service project, it seems to work fine.

Error message. "Please re-authorize Jira to create requests using request type and reporter fields in Jira Service Management project."

I've opened a ticket with Atlassian asking them to take a look at this. I invite anyone else on this thread to do the same to get some attention on it.

All - Anyone ever have any success (ever) getting Atlassian to pay attention and look at an item like this?  Struggling to understand what opens exist.  This is disappointing.

We are also affected by this issue. It is a pity that no Atlassian employee forwards the issue to the right place and has it fixed.... Surely there is a team that has programmed this add-in, which certainly knows what to do to fix the bug.

Can we please get an update on this issue?

We are also affected by this issue.... I hope this will be fixed soon. We heavily use this plugin and would love to use this for JSM-Projects.

One thing we discovered was, that it is possible to use the send to issue function for JSM-Projects. It seems only the create issue function does not work due to the re-authorization bug.

mbamba activity log ends on Nov 20th.

I use as workaround Workmanagement Projects. You can create issues there and then move them over to the JSM-project.

mbamba@atlassian.com Please provide some update. Will this be fixed anytime in the near future or should we seek out a new tool?

Please fix this issue, thank you!

is Atlassian even looking at this issue !!??!?! 

Simply not acceptable !!! Taking more than 60 days to clear this bug. 

Please fix this issue, thank you!

My team would love to be able to use this plugin!

We would like to be able to use this plugin.

My team is also affected by this.

The plugin has a bug when opening a new service project issue.

Please prioritize this issue. This affects my team. Thanks!

This issue has been open for 90 days and there are still no updates?

There is a problem when opening a new service project.

If you all haven't already, *have your whole team click the "this affects my team" button* on this page. 

I was referred to this issue from Atlassian Support, who recommended that I have my team do that. Hopefully that will help escalate this.

f0d27f0175f2 5fa588be5eb0 bf1c7c1b7f73 ccaa3e38bbba 30bc7159f1b7 977c6cbc29d2 ea593686a2d8 299407033e53 055ca1bbc790 b23f47ed684a a0e9e1c1f76e 8543d45b4786 

We are having the same issue. We cannot create new issues from Outlook. Please prioritize this issue. This is affecting our workflows.

Has anyone at Atlassian seen this?

Is there any update to this, I am also having this issue that I have used daily for logging tickets seamlessly out of Outlook. Any escalation that can be done?

Same problem here. Unsure how this is considered Severity 3-Minor.

We have the same problem!!!

We have the same problem!!!

I am experiencing this issue too.

We need this integration too! Please fix this issue soon.

Please fix this issue soon.

We utilize this integration all the time! Please fix!!

I am also getting these issues only effecting my Service Management projects.

I am also encountering this issue. Works with all other project types (Software, Work Management) but when you go to attempt to use it with the Jira Service Management project you get this exact problem.

Attempts to Resolve:

• Navigated to the Atlassian Admin > Products > Site > Connected Apps > Settings  > and set the User Installed Apps setting to "Allow" (it was on "Blocked")
• With User Installed Apps being allowed, uninstalled the Jira Cloud for Outlook (Official) app from the Connected Apps page
• Returned to the Outlook profile (Office 365, web-based Outlook) and uninstalled the Jira Cloud for Outlook (Official) app from the Outlook apps. Closed all Outlook tabs, then went back to Outlook and reinstalled the app. Still encountering the same re-authorize problem.
• Went to the app settings in Outlook and choose to "Disconnect" and re-"Connect to Jira", problem still occurs.
• There are no permissions on the JSM project that would prevent issue creation. The permissions scheme on the Jira Software project is nearly identical.
• When going to Jira > Apps > Manage Apps > Settings > and enabling "Enable development mode" then trying the above attempts to resolve again, the problem still persists.

Additional Details:

• The app does not show up in Jira  > Apps > Manage Apps > under User-Installed Apps  (/plugins/servlet/upm?source=side_nav_manage_addons)
• The app instead shows up under System apps
• When viewing the "Audit log" of the Jira  > Apps > Manage Apps > Audit log  there is a clear log of the installation and uninstallation of the app in Logs
  Installed "Jira Cloud for Outlook (Official)" (app-key "n/a", version "6.2.0", environment "DEVELOPMENT", app-id "660a41eb-72c9-47e2-bc9e-e773d2b1ee95")
• Why does this say "DEVELOPMENT" when other apps in the log say "PRODUCTION" for the environment? I'm guessing this is part of the problem. Perhaps Atlassian listed this app as "DEVELOPMENT" by accident?
• Additionally, the app-key is missing, which does not correlate to the key listed as "atlassian-outlook-integration"