Bug Report? Custom-Field Value options not preloaded for custom field in Filter.

Jeff Skaanland

When I select a custom field (Select List with Multiple Options) to filter issues, none of the options are available for tasks and subtasks. 

When those two issue types are excluded, the custom field values are populated.

When I create a JQL query using the custom field, the task and subtasks are correctly filtered, but switching back to basic view generates an error saying that field value isn't for the issue type... but it is.

Attached image. Additionally, attempted in Chrome  81.0.4044.138 and Firefox 76.0.1.

 

 

 

Nic Brough -Adaptavist-

No, that's not a bug, it is the system trying to give you the least confusing answer.

I suspect your multi-select list has two "contexts" (possibly more, but the case of two is enough to explain it).  One of the contexts is for tasks and sub-tasks, the other for all the other issue types.

Each context has its own list of options for the values in the field.  Imagine a simple one where your field "Colour" contains Red, Green, Blue for stories and Cyan, Magenta, Yellow for sub-tasks.

What you're doing in your filtering is selecting Green, then swapping to an issue type where Green is not valid because the options are Cyan, Magenta or Yellow.  That's why you're getting "FW is not valid" - it's not on the list for this project/issue-type

When Jira is being asked to look at both types, it has no way of knowing which context you might be interested in, so it has two choices - offer all the options, or offer none (making the point that there's a context problem here).  Offering all the options is not what Atlassian chose because it is more confusing for us humans.  Imagine a case where you've got hundreds of contexts, or contexts that contain the same label for different options.

Now, imagine you add "Black" to both of my colour contexts.  That's fine, but you have to remember that the options are totally different items.  They have to be, because they're in different contexts and have to be unique. no matter what their label is.  You may have done the same with FW, which is rather confusing (There is an improvement logged for having cross-context shared options, but it's not moving very fast).