Renaming a System Field in JIRA (must remains Project dependant)

[Isabelle HILD]

Hi,

We want to rename the system field 'Component in Beamline, but this must be done for one project only, without impact on other projects housed in JIRA.

I saw already the topics below, but is it possible to make these changes only relevant for one Project?

https://confluence.atlassian.com/display/JIRA051/How+to+Rename+the+%27Priority%27+Field+in+the+Issue+Navigator

https://confluence.atlassian.com/display/JIRAKB/Renaming+System+Fields+in+JIRA

Any other solution?

Thanks a lot in advance for sharing your advice and knowledge on this subject...

Cheers,

Isabelle Hild

[MatthewC · Accepted solution]

Not for a single project, no, at least none that I could think of. You have to remember places like the issue navigator could contain data from any number of projects.

Depending what you are trying to do, why not create a custom field the way you want it, then use a field configuration scheme to hide the system field for that project?

[Isabelle HILD]

Hi Matthew,

Thanks a lot for your answer.

Actually, I thought of the possibility to use a custom field, and hide the "Component" system field.

But besides, the possibility to have a default Assignee related with each component is very useful for this project.

So we will try in a first time to keep "component" as it is, with its features, and see if this naming question is a real problem for the users, or if they will just forget the point in two days...

Have a nice day.

Isabelle