Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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.

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

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... 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

322 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you