Many custom fields with same name.

I have 6 fields with name "Priority" so when i map a one of those field priority to a project and create issue, after that when i search issues through issue navigator of that project i will get created issues and when i wanna configure coloumns if i give priority in search box i am getting option to select one of the five priority.. but i have mapped only one priority to the screen and that screen is mapped to this project. so i should get only one priority feild right..? why i am getting five priority list?? any idea friends ?

1 answer

1 accepted

This is so, becuse the navigator always lists all available fields on the system when configuring columns. There is no way to know the context in which you want to select columns as in the issue navigator you can see issues from many different projects.

Having custom fields with same name has many "bad" effects in the UI, so try avoiding that (Yes, I know that sometimes this is not easy as there is no way to set a "display name" different from the field name)

I don't think there is a solution for that

tnq for ur suggestion Boris.. but see i have 6 fields in name Priority in that only five i can see as a admin and only four as a normal user in issue navigator while configuring coloumns.. any solution to avoid this? i have filtered all issues of one particular project.

but my point is.. see i have 6 priority field.. but i can see only 5 in configuring column as admin and 4 in configuring column as normal user in issue navigator.. why..?

I suspect that depends on their configurations.

I very strongly recommend that you rename the custom fields, otherwise you'll never work this one out. I'd go for something innocuous like adding punctuation to the names. You'll need to do this because my first and second questions are "which priroity is never offered to you, and which one appears when you're an admin and not when you're a user?"

Another thought - does the user already have the priority in the navigator columns? Jira won't offer it again if it's there already.

Isn't it possible to have a JIRA feature that doesn't allow to create field with same name?

Suggest an answer

Log in or Join to answer
Community showcase
Alexey Matveev
Published Saturday in Jira

How to run Jira in a docker container

Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...

598 views 6 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot