I want to add 2 context for same custom field and for same project but for different Issue types ?

[Tanu Ranjan Bharadwaj]

Hello,

I have this custom field of type select list by the name of 'A'  which has 2 sets of different values for 2 different issue types but for the Same project. 

So, is it possible to Configure the same by using Context in that custom field for same project but for different issue types ?

[Krisztian Kovacs · Accepted solution]

Hi @Tanu Ranjan Bharadwaj

Sadly no: https://jira.atlassian.com/browse/JRASERVER-6851 and it seems final. :(

[Nic Brough -Adaptavist-]

Frustratingly, you can do context by issue type, OR by project, but not both on the same field.  So if you have two sets of values for a custom field and want to do it by issue type, it's global, for every use of that field in every project.

[Tanu Ranjan Bharadwaj]

Thank you for the update.

[Tom Hudgins]

@Nic Brough -Adaptavist- I can't get - what I think you are saying - to work.

I have a custom field with a context that is global and a specific issue type. If I try to make another context, I can select a different issue type but I have to chose a project (I can't leave it global). I read your statement as I could have two global contexts, each with different issue types but that doesn't seem to work.

Am I reading your statement wrong or am I doing something wrong?

Thanks

[Nic Brough -Adaptavist-]

You're not reading my statement wrong, you have understood it fine and run straight into the second part of the problem where my answer is totally lacking any detail and hence very very unclear.

I think the problem is the complexity of the possibilities.  I've always imagined a multi-context system to start with "here is a default you use everywhere", and then you could define other exceptional contexts by project or issue type, or a combination of the two.  

It's easier to explain this with an example.  With my scheme, you could now set up contexts like

• Default  (field options = Red, Orange, Yellow, Green, Blue, Indigo, Violet)
• Issue type = bug (field options = Cyan, Magenta, Yellow, Black)
• Project = ABC (field options = Red, Green, Blue)

Sounds fine, but what happens when project ABC has a Bug issue type?  Which context kicks in?

There are ways to fix that, with a bit more config and code, but Jira "solves" (quotes because I think it's a total cop out as a solution) this by simply not allowing it.  There's no problem having a global/default context, but then additional contexts have to be done by project AND issue type, to avoid the problem in my example.

[Tom Hudgins]

Hmm. I get that there can be conflicting permutations in some cases but I can't even do what seems to be the simplest thing - a select list, for a single project, that has two different option lists for two different issue types. 

I can make one context global with issue type A, and then another context project specific with issue type B, but the field doesn't show on a screen for issue type A. "Where's my Field" says it's not configured for the scope of the issue type/project.

[Nic Brough -Adaptavist-]

That's correct, that's Atlassian completely ducking "how to deal with conflicts".

[Paul Mugridge]

Why is this marked 'solved'?  It should be marked 'ignored'.  

[Nic Brough -Adaptavist-]

The community is not a support or feature request system, it's a forum, and people are asking questions.  The "solved" flag is there to say "this question has been answered usefully", not "the thing we're talking about has been fixed/implemented/made redundant etc".

That information is over in the issue Krisztian gave us a link to.

[Oliver Wasiak]

There is the possibility to provide feedback to this feature implementation. Maybe it would be worthwhile to provide the feedback here: https://jira.atlassian.com/browse/JRASERVER-72239