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
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
I have inherited a JIRA Service Desk project in which the prior admin configured essentially a one-to-one match between Issue Type and Customer Request Type. All of the Issue Types share the same Workflow, Screen Scheme and Field Configuration. In other words, there is nothing different about them from the Agent perspective.
My inclination is that remove them and have a single issue type that is reused for all Customer Request Types. This would work without any problem. However, I understand that initial motivation, which is to make it easy for the Agent as well as reporting to differentiate between the types of tickets that are raised. While we can look at the Customer Request Type, it is painful to have to do comparisons based on the internal value rather than the text value.
As a general question, what are the pros and cons of using multiple Issue Types that represent different types of Issues even though the workflow and fields are the same?