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

URGENTE! Alter locked fields infos

Dionei Piazza

We renamed the issue type Epic to Quest. So what used to be Epic Name, Epic Link, Epic Description, now it makes more sense to have Quest Name, Quest Link, Quest Description labels.

Somewhere I read that these are Locked Fields, and that these fields cannot have their settings changed. Is that right or is there any way to change it? And if I change, will I be at risk of links between issue types?

Accepted answers

Nic Brough -Adaptavist-

You can not change locked fields on Cloud, and probably shouldn't be messing with them on server either - they are locked for a reason - to prevent them being misconfigured

I would very strongly recommend that you put the name Epic back in place. Jira Software works with a rename ok, but a lot of apps do not. Please, rename it back to Epic (This is likely to change in the future as Align does not use Epic to mean the same thing, but for now, do not rename Epics)

All comments

John Funk

Hi Dionei - I cannot urge you strongly enough to change it back to Epic. You will encounter so many problems that I can't even begin to describe. My bottom line recommendation - DON'T DO IT!!

Dionei Piazza

Hi @John Funk , grateful for your concern.

So far we have only changed the name of the issue type through the Jira issues configuration panel. As far as I know, this change does not cause any problems. Can you name a problem caused by changing the name of an issue type?

I think there is a risk in "changing locked labels" and their settings. Is this where the danger you mention lives?

John Funk

Here's a link to some more info/points of view:

https://community.atlassian.com/t5/Jira-questions/Why-is-my-custom-field-locked/qaq-p/1000282

I don't know if exactly every problem that would erupt, but most likely it would cause add-ons to not function correctly at a minimum.

Nic Brough -Adaptavist-

You can not change locked fields on Cloud, and probably shouldn't be messing with them on server either - they are locked for a reason - to prevent them being misconfigured

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

field