how i make severity default in new project

[Orel]

hello, when I open a new project I need to add the severity, and when I open a new project, the severity that I had before disappeared, so how I add the severity in all of my new projects permanently? thank you

[Boris Georgiev [Appfire] · Accepted solution]

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)

[Boris Georgiev [Appfire]]

I don't think there is a solution for that

[Nandeesh M S]

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.

[Nandeesh M S]

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..?

[Nic Brough -Adaptavist-]

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.

[Girish Jagdale]

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

[Denis Hunt]

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

[Shawn L]

@Denis HuntYes you can using the custom field context. You can remove the global context of the priority fields, and make that particular version set to a specific project.

1. Priority ("1") - Context: Project ABC - remove global context so it doesn't show to any other project.
2. Priority ("2") - Context: Project DEF - remove global context.
3. Priority ("3") etc, etc