How do I customize issue types without affecting other classic projects?

[Shawn Connelly]

Hello all,

Due to a blocker bug in Jira's next-gen project (https://jira.atlassian.com/browse/JRACLOUD-69225), I need to convert a next-gen project to a Classic jira project. 

This next-gen project employs customized Issue Types (none of the default issue types are used), so I am unclear how to customize the issue types without affecting our other Classic Jira projects, which all use the default issue types. I think I need to create a custom Jira workflow? 

Can anyone explain how I can accomplish this... perhaps point to a tutorial?

Thank you,
Shawn

[Angélica Luz]

Hi Shawn,

Thanks for reaching out to Atlassian Community!
If you are talking about customizing issue types for a next-gen project, it won't affect any classic project, because next-gen is an independent project, so any issue type that you create or modify on a next-gen project will only change for that specific project.

If you are talking about issue types for a classic project, each project has an issue type scheme that you can find on Jira settings > Issues > Issue type schemes.
On the same page, but on the left sidebar you can see "Issue types". On this page you can edit and also create new issue types. If you change the name of an issue type, it will affect all classic projects, so my suggestion is for you to create new issue types with the desired names and icons and then on the "Issue type schemes" page, you can associate the issue types with the desired project.

Hope this helps!
If you have any other question, please let us know.

Regards,
Angélica