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; } } }

Change vs Change request?

Mariano_93cg92

Hello! I ran into these two different issue types, which seem to come out of the box with Cloud:

I tried creating both to see the differences, and there seems to be none. Is it only the icon that changes?

I would like to keep Change and rename it Change request, as the icon differenciates from the subtask, so it will be easier to visually identify it.

I would love to hear your opinion on how to manage change requests in a simple way as well!

Take good care.

Accepted answers

Joseph Chung Yin

@Mariano -

First of all, Jira Software/JSM out of the box doesn't include "Change Request" issue type. You should check with your other admins to determine if he/she created the issue type by accident. By default - "Change" issue type is provided via JSM and a custom WF "Change Management workflow for Jira Service Management" associated with it.

My recommendation is for you to delete/not to use the "Change Request" issue type and just use the "Change" issue type. If "Change Request" is needed, then you can change the name and icon if you have the appropriate permissions.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

All comments

Walter Buggenhout

Hi @Mariano,

You can create as many issue types as you want in Jira and you are totally free to name them however you like. That is most likely what happened here. I don't think the second change request came out of the box, as built-in features normally have a description.