You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am using a copy of the SUP: Service Request Fulfilment workflow for Jira Service Management workflow in JIRA. When it was copied the transitions were messed up and now my tickets statuses will not automatically update.
All tickets come in as Waiting on Support status. When we reply to the customer with a comment in the ticket we want the status to change to Waiting on Reporter. And vice versa when they reply back to change back to Waiting on Support.
How do I create this transition so this status update is automated?
So ultimately you’re going to need to go into the workflow and edit that workflow and straighten it out. I’m unsure how things: “got messed up”. One thing to keep in mind when you go to edit the workflow is that if that workflow is used by other projects then you will want to make a copy of the workflow rename it and then associate it with your desired project after you edit it. This is so that you don’t change the behavior for other projects.
to add the workflow, as a project admin or Jira admin, click on project settings then workflows and find the workflow for the issue type you’re interested in and click on the pencil to edit.
So below is an example of an older test project I have that uses legacy automation for this purpose. I suspect or rather I’m sure there is a method of doing this with the new automation as well. So you can look at either approach for achieving your goal.
So something is amiss with the Community and I can’t post images so here is the text version…
When this happens...Comment added
If these match...Issue matches:Status = "Waiting for support" AND "Customer Request Type" is not EMPTY
Comment is public
User is not a customer
Comment is primary action