Field Context: One CF - One Project - diff options based on Issue Type

[Yana Stoliarova]

Hello!

I have a project CBLOS and two Issue Types: Feature and Epic

The requirement is to have different list of options for a field 'DoD' based on Issue Type.

When I tried to accomplish it using two Field Contexts I faced a situation that I cannot select the same project in both schemes. 

What would you suggest?

[Fabian Lim · Accepted solution]

Hi @Yana Stoliarova

This is a known issue with jira. You will have to create a context by issue type globally instead.  

Good luck.

[Yana Stoliarova]

I decided to create separate fields instead: Feature DoD, Epic DoD.

[Fabian Lim]

Excellent.  That was the other option I was going to mention, glad you were able to figure out it on your own.  

[Suvarna Gaikwad]

@Yana Stoliarova as per your screenshot, it is already applicable for CBLOS and DEV project. You can read note below Configuration scheme for DoD(Feature)

[Yana Stoliarova]

Because DoD (Feature) context is Global - not particular project. I want to select 'CableOS' (CBLOS key) project instead. So in Jira DB the 'DoD' field will not be present in other projects at all.

[Suvarna Gaikwad]

@Yana Stoliarova workaround is to create another custom field with same name and required context. Screens needs to be modified to include this field as well. This is not clean solution though.

Else if you have script runner, behaviours feature can be used to achieve this with little bit of scripting.

[Yana Stoliarova]

Thank you. Yes, I decided to create two fields but because I hate having duplicated custom field names in a system, I created: 'Feature DoD' and 'Epic DoD' with proper contexts.

Thank you

[Suvarna Gaikwad]

@Yana Stoliarova great to know. if it solved your problem, kindly accept my answer.