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

Linking 2 different workflows together

What about linking workflows together so that the issue type changes automatically?

1 comment

The best answer to that is a simple "no".

The issue type is a fundamental indicator of the type of thing you are doing.  Because it's generally immutable (the only good reason for changing an issue type is "the person creating it chose the wrong type"), Jira simply does not expect it to change as a matter of course.

There is a lot of configuration hanging off the issue type, including the workflow it uses.  Having a process that changes itself to another process part-way through is a nightmare in real lift, even before you begin to code for the computers to do it.

You should look at why you think you want to change the issue type.  If it's not because a human picked the wrong one, then it's almost certain that you are not mapping your processes into Jira correctly.

Comment

Log in or Sign up to comment