What is the impact of changing the name of an issue type?

[Hooda Abdullah]

In a live system, if I change the names of our issue types is there any adverse impact?

For example - we have an issuetype "Improvement"  I wish to change the name to "Non-Functional".

I understand that any filters using "improvement" will have to change but are there any other impacts I haven't thought of?

I also wish to rename "New Feature", and "Task",  but want them to all continue to work in exactly the same way (no changes to workflow).

Hope someone can confirm this is a cosmetic change with no hidden side effects.

Thanks,

[Alexey Matveev]

Hello,

If you have saved filters, where you use this issuetype in the JQL query, they will stop working. Or if you have scripting add-ons and you referenced this issuetype by name, these scripts will also stop working.

[Hooda Abdullah]

Thanks.  I was aware of the impact to filters - will have to check scripted add-on and other utilities.  

[Gregor Kasmann_Actonic]

These object types may be affected:

• Filters (Dashboards)
• Recurring tasks based on JQL
• Groovy, SIL, other scripts, which uses issuetype names
• Service Desk Automation, Jira Automation and other add-ons, which uses JQL