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

What is the impact of renaming an issue type in Jira Software ?

Arunajyothi Samala

Renaming issue type from R2D2 capability to GTM release bundle

this field is used few of the SIL listeners, used in Advance roadmaps Hierarchy.
how do I find overall impact on the jira if we rename the issuetype?

What is the best approach other than renaming an issue type?

Accepted answers

Mykenna Cepek

The native functionality in Jira will be fine when things are renamed -- things like multi-select drop-down menus (for Issue Type in your use-case).

Anything custom coded is likely to break. This would include JQL or IQL (as in SIL), since specifying an Issue Type name in text is, in hindsight, brittle to renaming an Issue Type.

The underlying id (database primary key) for the Issue Type will be unchanged, which is why the native functionality will continue to work fine after a rename. But the name-to-id mapping will break. This isn't specific to Issue Type, but is a generic problem (not just for Jira, but for any such amazingly customizable tool).

Other examples of this "naming brittleness"' include Project Key, Component name, and more.

I haven't tested it, but I wonder how Jira Automation rules would cope? I suspect they store IDs, but it would be worth testing as another possible area of breakage.

All comments

Mykenna Cepek

The native functionality in Jira will be fine when things are renamed -- things like multi-select drop-down menus (for Issue Type in your use-case).

Anything custom coded is likely to break. This would include JQL or IQL (as in SIL), since specifying an Issue Type name in text is, in hindsight, brittle to renaming an Issue Type.

Other examples of this "naming brittleness"' include Project Key, Component name, and more.

I haven't tested it, but I wonder how Jira Automation rules would cope? I suspect they store IDs, but it would be worth testing as another possible area of breakage.

Arunajyothi Samala

I did some SIL scripts, so I will go ahead and rename them. How to I find JQL queries that is being used as filters/reports/gadgets for that old issue type?
How do I find what automation rules are being used with specific to that issue type?

How do I find the places to look for a break-down that is caused due to renaming issue type?

Mykenna Cepek

How to I find JQL queries that is being used as filters/reports/gadgets for that old issue type?

It looks like you're using Jira Server, so you can probably query the Jira database for filters to inspect the JQL there.

Gadgets - maybe also in the DB (??), but vendor-added gadgets might get tricky. Maybe just wait until people complain and fix what people notice?

I have no experience with querying the Jira DB directly. There are community posts with some of that info, maybe search around?

How do I find what automation rules are being used with specific to that issue type?

This might be easier. If you're a Jira Admin, I think you can export all Jira rules (global and project-specific). Then you could just text-search the exported JSON. It's ugly, but it may be the easiest way. A JSON pretty-printer will help you visually parse the automation rules to be able to track down individual rules.

How do I find the places to look for a break-down that is caused due to renaming issue type?

The above will cover a lot of it. Jira Add-Ons (Apps) might be another area to explore. I can't help there. Of course any integrations with other tools, or uses of the Jira REST API will need to be reviewed as well.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server