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
As you are going thru a standard development flow, I would like to set constraints for a given workflow step. An example would be you can not go into a development step without the Estimate field <= 0.
Hello @Dave Kuipers
Welcome to the Atlassian community.
There are two ways to set requirements on transitions - Conditions and Validators.
If a Condition is not met, then the transition will not even be presented to the user.
With Validators, the transition is available. The Validator is applied when the user clicks the button to save the transition. This is useful when you want to prompt the user to enter a value as part of the transition.
The terms Condition and Validator are used in the documents for modifying workflow for Company Managed projects.
Modifying workflows for Team Managed projects is a bit different. The terminology is different and the UI is different, and the options you have for conditions and validators is more limited.
With which type of project are you working; Team managed or Company managed?