Can a custom field have multiple contexts under the same project?

Edward Moxley

I have a custom (assets) field that I want to expose on an issue as a single value select for some issue types, and a multi-value select for other issue types, within the same project. I tried to configure different contexts, but that didn't work as planned (the field didn't show up in some issue types).. And yes, I made sure I selected the appropriate issue types for each context. When I specified the project in one context, it didn't allow me to select it in another context. When I made one context global and then created another context for just some issue types in my project, the field didn't even appear for those issue types.

Is there a solution or workaround? Or do I need to create 2 custom fields; one for single values and one for multi-values?

 

Thanks for considering my question.

Stevan Mandić

 

@Edward Moxley  When creating a new context for a custom field, you can only change the default value and options and apply that context to a certain issue type (project).
If your custom field is single-select,  creating a new context will not allow you to switch to multi-select options.
The solution is to create separate custom fields, one single-select, and the other multi-select.