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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Team!
We have a status Triage. Triage has 4 (send to team yellow/ send to team red/ send to team blue/ send to team product) transitions to one status (project work)
I'm trying to write an automation task for this particular case that IF Send to team red transition is used then make some changes (such as change issue type, change some additional fields, etc) However JIra automation only allows to specify that IF changed FROM triage TO Project work THEN execute the actions. Is there a way to point to automation to look at this specific transition?
Hi Arturs,
What happens when you execute each transition? Are you setting some kind of value? If so, then you can use that value for the condition.
we have separate teams (as an example we have a field "teams" and each board is separated by this field value) So the idea is to execute this transition (example send to team red) and instantly automation is executing a couple of rules (change the field of teams to red, notify slack, etc)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How are you actually setting this value? Is it a field? Assignee? etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is a dropdown field (but there are other things that need to be changed) we have a separate tracking of bugs (for instance Support bugs is one issue type AND teams, such a team red, has separate issue type of Project bug) So moving issue to another type is one of the things I need to do out of this automation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then you can create an automation rule with a trigger on Field value change.
Then add a condition if the value is Red Team, then add an action for Edit issue and set the values for the fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh so I change it on a transition level within the workflow and then based on that I create automation. That should work. Thank you @John Funk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.