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.
Join now to unlock these features and more
The best way to do this is with "conditions" in the workflow.
If, for example, you have a field with options of red, green, and blue, then you set up your workflow so that you have the transitions
Then you can put a condition on the first one for "only allow if team set to red", and a condition on the second for "only allow if team not set to red".
Another way to do it might be to have an automation that looks at the field and moves the issue into the right status if a user gets it wrong.
@Nic Brough -Adaptavist- thank you for your reply but let me know more details
Iam using JSM datacenter version
which condition did you used also the condition is on transition so the same button in portal will send the request to next phase based on the condition correct?
It does not work that way.
You create two transitions with names as similar as possible to each other. A condition removes the transition from the list if it is not met, so you will only ever see one transition.
I've almost always done this sort of thing with Scriptrunner conditions. I remember that I had to write my own app to work with custom field based conditions in Jira 2, and I don't believe there are any built-in conditions that check custom fields (the built-in ones mostly work with users), so you will probably need to find an app that can add something.