How to trigger a status change when a reply is received?

Denise Droscha March 12, 2020

Hello, I want to create a trigger that will change the status to 'reply received' when someone replies to a ticket by email. How do I do that?

1 answer

1 accepted

1 vote
Answer accepted
Ansar Rezaei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 12, 2020

Hi

Consider you have 'reply received' status in your desired workflow and have transitioned from the status which you are waiting for reply form customers, Go to <jira-url>/servicedesk/admin/<project-key>/automation and click on Transition on comment.

image.png

 

There are lots of configurations there you can use. If you explain your problem more, I could help you with more details.

Ansar Rezaei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 12, 2020

I check the Cloud version. The same exists, and you could find it in the project setting.

Denise Droscha March 16, 2020

I'm new at making transitions and status changes and am not a developer, so my knowledge is limited. In my typical scenarios, I only have a parent issue and no child issues. I want to force a status change from any status to 'reply received' when either a customer or an outside person replies to a ticket. I don't see how to create that type of action.

Thank you.

Ansar Rezaei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 16, 2020

Is it a classic service desk project or Next-Gen one?

The following guide is valid for classics. If you have any trouble, let me know.

Add a new status to your workflow with the name "reply received". Workflow editing is available from here:

https://<yoursitename>.atlassian.net/secure/admin/workflows/ListWorkflows.jspa

and after editing, it looks like this:

Screen Shot 2020-03-16 at 9.12.36 PM.png

 

 

Then 

Go to the project setting and find automation on the menu. Then you see there are some preset rules. Pick the one with this name: Comment updates reply status and edit it or create a new.

If it's not clear enough yet let give me a WhatsApp call or Anydesk remote to help you more with it.

Denise Droscha March 16, 2020

It worked! Thank you for your help!

Like Ansar Rezaei likes this
Ansar Rezaei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 16, 2020

You're Welcome. So please hit my answer as Accepted :-)

Denise Droscha March 24, 2020

Ansar: can you help again? The automation rule worked one time but hasn't worked since. Here's a recap of what I use, the explanation of roles and the rule set: 

I am using Next-Gen service desk and the admin and main user.

I work in a franchise organization. I create Customer groups for the local offices to then access JIRA to open or update tickets for me to work on.

The tickets are for the customers each local office is servicing. 

I communicate with my JIRA 'customer' (which is the local staff) and with people outside of the project (true customers and vendors). These people don't have login access to the system other than to receive and respond to email I send using the JIRA email add on app.

I want an automation rule set so when a person that is not a JIRA customer and not me responds to a ticket, the status of that ticket is changed to 'reply received'. 

As previously suggested, I created a 'reply received' status in the workflow

I edited the automation rule for comments received. That rule is: Comment is primary action, user is not an agent and user is not a customer, update the status to 'reply received'. 

I am still not getting updated tickets. Can you help?

Like Ansar Rezaei likes this
Ansar Rezaei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 26, 2020

Did you check the log of automation?

Screen Shot 2020-03-27 at 8.36.59 AM.png

 

If you see this page in your instance, You can see what happens for each occurrence of calling this automation.

Here You can click "Show details" to get more information:

Screen Shot 2020-03-27 at 8.41.23 AM.png

If it's not clear for you please give me a screenshot of that page.

Christoph Reuter
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 7, 2023

Hi Ansar, I am having the same problem (using Next Gen)
I have created an Automation which should work and the Log File even mentiones, that it found the ticket in which a reply / comment was sent in via email.
But it shows an error message, that the new status cannot be resolved:

translated from German to English: The target status could not be resolved. If you use a smart value, make sure that it resolves to a numeric status ID or an untranslated name for operations (with the current status)

image.png

The underlying rule is easy:
triggered, by comment
When status is resloved
Change Status to e.g. waiting for support or open
(unsure about the exact English wording).
Can you help me with this.
I do not see customers answers and therefore have to open all tickets at the beginning of a day to see whether someone has replied.
Thank you in advance

Original German error message: Der Zielstatus konnte nicht aufgelöst werden. Wenn Sie einen Smart-Value verwenden, stellen Sie sicher, dass dieser in eine numerische Status-ID oder einen unübersetzten Namen für Vorgänge (mit dem aktuellen Status) aufgelöst wird

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events