You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all, here's a question for you since I couldn't find anything in the Atlassian Documentation:
Our customers sometimes use the wrong form (and wrong issue type/issue workflow) for some of their requests. So sometimes, our agents have to change an issue with the "Service Request" type to "Change" type.
These issue types use different workflows, however. In our case, a "Change" needs to go through several approval steps. We would like to enforce that, whenever an issue is made a "Change" that these always start in the first status in the workflow.
How do we enforce this?
You cannot enforce this to my knowledge. The mapping of the status is always done manually when changing the issue type.
One way you could enforce it is to close the Service Request with a specific resolution and ask the customer to re-submit the request as a change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.