Custom Field Context not working as I intend

[Sarah Aubuchon]

I've read that I can have only 1 custom field context configured per project so I would seem that if I really want two, then I need to configure the other based on just issue type or as the default. The custom field I cam using is a User Picker field and what I'm essentially looking to do is have some issue types in the project use 1 group as the available filtering for the user picker and another issue type in that same project to use a different filtering option. 

So project change with issue type normal will have group xyz as the available users to select in the field and same project change but issue type emergency would have group zyx as the available users to choose from. 

When I configure context 1 to be project change and issue type normal, everything works well. When I configure issue type emergency with no project selected since I cannot select change twice, and set that filtering to zyx, the right people are not appearing in the list.

[Joseph Chung Yin · Accepted solution]

@Sarah Aubuchon -

Unfortunately, a project context setup of a custom field can only be one.  You cannot have two different contexts of the same field for a same project for two different issue types used within the same project.

In this case, you will need to create another custom field to support the emergency issue type for the project. 

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Sarah Aubuchon]

@Joseph Chung Yin  Shouldn't the global context with the Emergency issue type work too?

[Joseph Chung Yin]

@Sarah Aubuchon -

It will not because a context is already created for your specific project.  This context is always used by default now.

The global context will be enforced for any other projects that use the field.  So it is not a best practice to setup a global context that way in my opinion.

Best, Joseph