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

Need build a workflow base on user custom field conditions

we have a custom field and want to start a workflow based on the content.

I have made a list of radio buttons. I want to let the user chose one of the options and then continue the different flow according to the different options.

I think this workflow is performing checks on a field itself, not on its value.

How can I achieve this?

2 answers

0 votes

You will need to find a way to add conditions to the workflows (the ones built into Jira off-the-shelf are not very configurable when it comes to custom-fields)

Once you've got a method for creating conditions, edit your workflow - you 'll need to create all the different transitions you want to allow depending on the options in your field, 

Then on each transition, add a condition that blocks it unless the field is set to the right value.

Note that if you want the action of editing an issue and setting the field to also perform the transition, then you will also need a listener to catch the edit and execute the relevant transition.

Hi @jacky_wang,

You could design your workflow to allow for different paths, like in this (totally random) example:

Screenshot 2021-04-18 at 13.16.04.png 

In the example, any created ticket will land in status triage and from there can only transition to the Open status. I would recommend you make sure that your custom field is a required field before you can move into the open status (use a required field validator to make sure this is the case).

Once a ticket is in status open, specify a condition on every transition that goes from open into a next status. In the example, those are the transitions to:

  • Waiting for Approval
  • Waiting for Support
  • Selected for Development

Suppose that a Server Change must be approved. I can make sure this is the only available transition by using the following Value field condition on the transition to Waiting for approval:

Screenshot 2021-04-18 at 13.22.32.png

In the same way, I can provide appropriate conditions for the other transitions in the workflow. 

Transitions that don't match the conditions you specified will not be available to the user.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

840 views 28 33
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