Hello,
I would like to ask why an enterprise would choose to have different issue types for its issues. We are having JSD installed and in use for about 2 years now, using one single incident for different kinds of IT issues of one project and I was wondering if we should introduce new issue types and whether that would make our work easier or not!
Thank you in advance,
Aggeliki
Jack, Alexis,
Different workflows would be a reason for us to use different types in the future.
Thank you both for your answers.
Regards,
Aggeliki
Several possible reasons for different “issuetypes”:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Aggeliki K ,
different issue types can represent another issue lifecycle, and have its own workflow, custom fields, etc.
For example, you're only using Incident today. Maybe sometime in the future, you'll need to handle new features : in this case, the workflow might be different from the one for incidents, and the information you require will be different too.
That's (one) of the reasons why you can use different issue types in Jira.
Let me know if this helps,
--Alexis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.