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

Can we assign different priority names to different projects using Translate priorities?

Shashi Matha

We are trying to change the names of priorities from Highest, High...etc to Critical, Major...etc. I can see we can achieve this using Translate priorities.

However, this is changing not only Jira Service Desk project but all other internal dev JIRA projects.

How can we make this change only to JSD specific projects? We tried to see if there scheme for priority field but it looks like it is unavailable.

Hope there is someone who has done this without using marketplace add-ons.

Accepted answers

Dave LIAO

@Shashi Matha - hi Shashi! Unfortunately, translating priorities impacts those values across your entire Jira instance.

Workaround: If you want project-specific Priority values, consider creating a "Importance" custom field, and have project contexts for each set of values you want. (Jira lets you create your own "Priority" field but since you can't get rid of the system one, any JQL queries will refer to the field by its ID, which isn't the most user-friendly.)

I would also vote on JRACLOUD-3821 so Atlassian hopefully implements priority schemes in Jira Cloud.

All comments

Dave LIAO

@Shashi Matha - hi Shashi! Unfortunately, translating priorities impacts those values across your entire Jira instance.

I would also vote on JRACLOUD-3821 so Atlassian hopefully implements priority schemes in Jira Cloud.

Ste Wright

Hi @Shashi Matha

Translations are language-based, rather than project-based.

So for example, if the priority is set to Critical for Spanish, it will show as Critical in all projects if you also change your user account's language to Spanish.

Priority Schemes aren't available in Cloud - see JRACLOUD-3821 to vote/follow this suggestion.

Without an app, your options are limited - this is how I'd do it:

Custom Field: Use a custom field - such as a Select List (single choice). Having a custom priority field will allow you to have custom options per project using Custom Field Contexts
Automation: This is an extension of the Custom Field option, if you want different users to see different wording. Still create the custom field, but set the values based on the Priority field. So for example if "Highest" is chosen in the Priority field, have an automation rule which automatically sets the custom field to "Critical".

Ste

Shashi Matha

Thanks! Looks like this is not getting done even after two years.

Dave LIAO

😞

Dylan Kogut_oyddbr

@Dave LIAO Is there a reason that Jira is so reluctant to implement this?

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-desk

jira-service-desk-cloud