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.
Can the Automation for Jira app set a value for a custom field in a post function? I am trying to implement a "self-reflecting" transition.
I am finding that the Automation for Jira does not allow for a custom field to be set as a post function on a status transition.
Hi Boyd,
Can you describe your scenario in a little more detail?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am trying to implement a post function on a transition that sets a custom field and transitions the issue back to the same state. So, the issue in the Verify state initially has two transitions: Send back for More Work or Mark as Verified. When the verifier marks it as verified, a post function would set a Verified flag as "Yes". Then, the issue in the Verify state will have two transitions: Send back for More Work or Send to Closure. QA sends to closure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, I still don't think I am following it completely, but let's see.
Issue is moved by Verifier to Verify status. This sets the Verified flag as Yes. And then you want to transition to Send to Closure. Correct?
Otherwise, the issue is transitioned by the Verify to Send Back for More Work. And no automation is needed. Correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Issue is moved by Verifier from the Verify status to the Verify status . This sets the Verified flag as Yes. And then QA (different user) checks the Issue and, if acceptable to QA, wants to transition from Verify status to the Closed status using the Send to Closure transition that has a condition that only those in the project role of QA can do.
Otherwise, the issue is transitioned by the Verifier via the Send Back for More Work to the prior state, Implement. And no automation is needed, at last for the Send Back for More Work transition.
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.