Automation Plug in doesn't work correctly after update to Jira Core 7.2 and Service Desk 3.2

Hello Support,

we've update to JIRA Service Desk 3.2 with JIRA Core 7.2. After updating the following behaviour appeared:

We've a configured automation transition the status from "Waiting for Customer" to "Response from Customer" as soon as the CU is adding a comment in the Service Desk portal. (This was working fine with Service Desk 3.1.9). Now this has changed. As soon as our Agent is adding the question as a comment in transfering the Issue from in Progress to Waiting for Customer, this comment seems to trigger the automation already. As a result the issue is directly transitioned to the status "Response from Customer".

There are different workarounds (like adding conditions to the transition in the workflow to restrict this to certain groups or add a condition to the automation to filter for "not an agent". Unfortunately if we apply one of these workaround feedback from customers via email are not longer processed correctly. Seems the reason is the email handler is running as administrator.

What we wonder is - is this a bug in this update as it was working before?

1 answer

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,789 views 18 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you