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,456,632
Community Members
 
Community Events
176
Community Groups

Want to capture reason for transition change in workflow

With each transition change in our workflow, we want a selected list of values out of ALL values in our REASON custom field (dropdown) to appear. Simply said, this Reason dropdown has 20 values, roughly 4 each for each of the 5 transitions in the workflow. Now when I go from status A to status B, I do not want all the values to appear.

How can we achieve this? Any help would be greatly appreciated. 

3 answers

1 vote
Joe Pitt Community Leader Nov 02, 2015

Being in the cloud you can't use scripts so I don't believe you'll be able to do it. even so, every time you go through a status change the field will be overwritten meaning you'll need to look in the history for the values at each transition. The obvious work around is to have a different select list field for each status change. the advantage to that is it will be easy to see what reason was used for each status as each will have its own field.

Use the built-in resolution field and the jira.field.resolution.include property on the transitions to select a subset of values for each of them. Easier to maintain than custom fields... 

0 votes

With plain JIRA I would suggest different custom fields for each different set of REASONS you need. Let's say you have a transition "Postpone" and one called "Reject". You want different sets of reason to pick in each one. Create a custom field "Reason for postponing" and one called "Reason for rejection" offering the different seelctions you need.

If you can come up with two different issue types for each you may use the custom field context feature. However, you will not be able to get around to maintain two or more different sets of values I am afraid.

Best regards,
George

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events