Jira iOS shortcuts error - “There was a problem communicating with the app”

[D_M_]

Until recently, I’ve been successfully running the Jira iOS shortcuts Create Issue action and Set Issue Field Value action to create and update issues on Jira Cloud. But the actions are returning this error: “There was a problem communicating with the app.”  

Please see the attached pic of the simple shortcut and error message. 

The crazy thing is that the shortcut actions actually still create / update the issue in the Jira app.  But because the error displays it stops the shortcut from processing other actions, thereby breaking the automation chain. 

I’ve also tried running the 2 failed shortcuts on different devices with no luck. I have the latest versions of the Shortcuts and Jira apps installed.

Strangely, other Jira shortcut actions like Run JQL and Post Comment still work fine and don’t show the error.  

Please help. 

[Simon Stiefel · Accepted solution]

Hi D_M_, 

I am sorry you ran into problems!

We've identified a bug in recent versions of the Jira app that can make some Shortcut actions fail. We've fixed the problem and plan to release an update this week.

If you are a beta tester of the app, you can download the fixed version (v134+) through TestFlight. You can sign up to become a beta tester in the app ("Settings" -> "Be a beta tester").

Hope this helps,

Simon

[D_M_]

Hi Simon,

I tried the beta out in TestFlight and the errors I was seeing appear to be resolved! Very much appreciate this!

[Mitarbeiter ZUCH]

Hi Simon, I think this issue reoccurs in the latest version. It is not possible to create an issue via shortcut. Exactly the same behavior as in 2021.

[Simon Stiefel]

Hi @Mitarbeiter ZUCH ,

I apologise for the inconvenience!

We are aware of the issue and are working on a fix. We have a public issue tracking this problem: https://jira.atlassian.com/browse/JRACLOUD-85412

Thank you,

Simon

[Simon Stiefel]

Hi @Mitarbeiter ZUCH ,

We just released version 221.0 of the Jira iOS app to the App Store which fixes this issue.

Thank you,

Simon