Why does JSM use [system] in issue type names ?

Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 24, 2024

Hi All,

I've been asking myself this question a few times, but never found the answer.

Why do the default issue types in Jira Service Management have the [system] prefix ?

  • [system] Incident
  • [system] Service Request
  • [system] Problem
  • ....

No other Jira product use a prefix. There is no "[system] Epic" in Jira Software.

In all my JSM implementations i've created my own "Incident", "Service Request", .... issue types, and don't use the [system] issue types. I've never encountered any issues.

Does anyone know why these prefixes exist ?

Best regards,

Kris

 

3 answers

0 votes
Rik de Valk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 30, 2024

For some reason, Atlassian prefixes the JSM issue types that way. They have documented that here: https://support.atlassian.com/jira-service-management-cloud/docs/what-are-default-system-issue-types/ 

But they do not explain why, nor if changing the names affects any functionality. But in my experience, there is no impact in renaming the issue types. 

Have a nice day, Rik 

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 24, 2024

Hi Kris,

I have wondered that myself, and I don't know. But you are also fine to do what you have done. 

0 votes
Nikola Perisic
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 24, 2024

Hi @Kris Dewachter ,

My guess here is this is how it was implemented. Now was it a mistake from the developers, guess we will not know this. Interesting thing that you have noticed this.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events