Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,107
Community Members
 
Community Events
184
Community Groups

Automation for Jira: Can it set value of a custom field in a post function?

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.

2 answers

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.

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 07, 2022

Hi Boyd,

Can you describe your scenario in a little more detail? 

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.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 07, 2022

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? 

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events