Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

Can I associate a workflow with custom field value?

Pete P Rising Star Mar 02, 2021

I have a custom field called "Change Type" with 4 levels as values (Level 1, Level 2, etc.).  The values are set through automation based on the input from two other custom fields. 

How can I associate a separate workflow to each of the Level values of my custom field?

 Change Type

Level 1: Workflow A

Level 2: Workflow B

Level 3: Workflow C


1 answer

1 accepted

3 votes
Answer accepted
John Funk Community Leader Mar 02, 2021

Hi Pete - The quick answer is that you can't. Workflows are exclusively associated with Issue Types. So you would have to change the value of the Issue Type, but that can only be done by a Move if the issue types are associated with different workflows. 

Pete P Rising Star Mar 02, 2021

@John Funk , thanks I was afraid of that...   So I guess I'll have to use one workflow and somehow branch it based on the value of the field?

Pete P Rising Star Mar 02, 2021

@John Funk  are you aware of any apps that would  let me do this "move" to another issue type automatically on a transition? 

"Move" is not a trivial change of type, unless the two types have the same configuration.  The configuration that matters includes the workflow.

There are some apps that can change issue type, but you have to do a lot of work replicating the migration processes within them, especially when the workflows are different. 

I do not think this is the answer to your problem, I think you'll have to go with the branching workflow, controlled by conditions.

Pete P Rising Star Mar 02, 2021

Thanks @Nic Brough -Adaptavist-  and @John Funk for the feedback!

Like John Funk likes this
Pete P Rising Star Mar 03, 2021

@Nic Brough -Adaptavist- ,  @John Funk    FYI Bob Swift responded back with a positive.  I don't know if you will be able to view this video or not due to permissions but here is link demoing the process.  

"Yes, you can change the issue type based on the custom field value through a post function upon issue transition.
Once the issue gets transitioned to another, based on the custom field value the issue type is changing, please refer to the below Snagit video for the same."


So I will experiment with it today and see what happens.  Since my custom field is calculated prior to creation of the issue possibly I won't have much to do with updating statuses etc.

John Funk Community Leader Mar 03, 2021

Hey Pete - I can't access the video. But I still think it depends on whether the the issue type you are changing to uses the same workflow as the current value of the issue type. Yes, you can change those with no problem. 

But if they are different, then I am pretty positive that it will take a Move function. You might ask Bob the more pointed question as such. 

mmm, I'd worry about that too.   I can't access the video either, but I'd like to, as I'd want to see how it handles the cases where issue configs are different (especially workflow)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events