nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom Issue Type limit in JSM v8.16.1 on Data Centre instance

Scott Bourne

Hi all, long time researcher first time question asker.

Is there a limit on the number of custom issue types a single project may contain?

While JSM comes with the default issue types of Incident, Problem, Change, Service Request and so on I have created quite a few custom issue types for our customers and I'd like to know if the amount the project can take is limited before I commit to them how many I'm able to supply them.

Any and all assistance is greatly appreciated, thanks Community.

Accepted answers

Joseph Chung Yin

@Scott Bourne -

Hi Scott:

There is no limitation on the issue types for Jira/JSM projects. The only thing that you need to consider is the usage of the issue types. When creating custom issue types, always determine to see if existing issue types can be used first, and only creating them if it absolutely necessary.

It comes down to more issue types will result in more management overhead for your admins and project admins on the usage of them.

Based on my experience - Less is More.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

All comments

Gonchik Tsymzhitov

Hi @Scott Bourne ,

Welcome

So about the that limitation I have not heard.

At least on my one of instance used 29 issue types, 52 customer types in one project. Unfortunately, that's legacy which inherited to me. I am doing clean up, because it's bad practice of creating ticket.