Is it possible to create drop-down list specific to a project level?

[Deleted user]

Is it possible for each project to set up its own drop-down list with its own available choices in the drop-down list?

It would be great if you can point out the documentation in atlassian if there is an information about this as I haven't found it yet by searching.

Thank you very much,

Jenjira W.

[Deleted user · Accepted solution]

The answer for this is following Nic's response. Thank you very much.

No, that's not possible yet - project administrators can only maintain versions and components for their projects.

It's quite a difficult thing to decide how to handle - whilst it's a common complaint that Jira doesn't support project admins being able to maintain their own fields, there's an equally large number of complaints that versions and components are maintained locally and aren't drawn from a common list like custom fields, and a huge concern that letting project admins do this would allow a huge proliferation of fields and values that aren't needed. It's a tricky problem to solve.

[Jon Sword]

Hi Jenjira,

This can be done quite easliy. This is called a Custom Field Context and it can be configured for different projects or issue types.

Take a look at this documentation and scroll down to "Adding a new Context"

http://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field#AddingaCustomField-CustomFieldContext

Cheers,

Jon

[Deleted user]

Hi Jon,

Thank you very much for your prompt advice. Having booked into the documentation, JIRA system administrator can add new fields into JIRA. However, is it possible for each project adminsitrator to configure which choices they want to have available in the field?

For example, System admin add new field "Another SW version" field

Project A set the field's options 1.0,1.1,1.2

Project B set the field's options 2.0,2.1,2.2

Cheers,

Jenjira

[Nic Brough -Adaptavist-]

No, that's not possible yet - project administrators can only maintain versions and components for their projects.

It's quite a difficult thing to decide how to handle - whilst it's a common complaint that Jira doesn't support project admins being able to maintain their own fields, there's an equally large number of complaints that versions and components are maintained locally and aren't drawn from a common list like custom fields, and a huge concern that letting project admins do this would allow a huge proliferation of fields and values that aren't needed. It's a tricky problem to solve.

[Deleted user]

Thank you very much for your reply,Nic. It would be great if you could share tickets you know about this request. So far, what I got from searching through JIRA support page is https://jira.atlassian.com/browse/JRA-1991.