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

Request Type name change implications?

Jared Grywacheski

We have a customer that would like to change the name of a couple of their Request Types - by doing this will this affect elsewhere in the Project where the Request Type is mentioned/used?

ie. Automations rules, Queues, Forms....

Will the name change propagate throughout these various tools or will the customer also need to go in and edit/recreate these?

Accepted answers

Manoj Kumar Gangwar

Hi @Jared Grywacheski, Yes, it will impact the automation rules & Queues. If the Request Type condition is used. Then, you have to update the automation rule with the new request type.
For the queues, you have to update the JQL query and replace the request type with the new one.

All comments

Manoj Kumar Gangwar

Jared Grywacheski

@Manoj Kumar Gangwar Thank you! and just to clarify, this won't be a new Request Type just a name change on an existing Request Type.... does that change anything?

Manoj Kumar Gangwar

Yes, if you re-name an existing request type and you have some automation or queue created where you have used "Request Type" = ABC, and later you renamed it to XYZ, then the automation rule will stop working and the queue will not show the newly created issues.

So, before re-naming, I would suggest that you check the existing automation rules If you have any conditions based on the Request Type, then update the conditions after the re-naming. Same for the queue, check all the queues, if you have used the Request Type in the JQL, then update it after renaming.

Jared Grywacheski

Great, thank you for the quick response.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management