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 ?
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 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.
My org is having a similar problem - we need to be able to easily query against custom fields for given projects.
Unfortunately trying to somehow make the displayed field name seem unique will not scale for us (we have dozens of projects with unique definitions of some fields like Priority). So, for now, the person querying needs to know which of the unique cf IDs is the one they need - i.e not a great solution !
Is there any way to somehow explicitly bind a custom field name definition to the project it pertains to ? Or, to limit which custom fields are visible to a given project member ?
NB I understand implementing this would possibly require an increase in complexity for Atlassian's schemas and changes to its query language so maybe wishful thinking...
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG