Agile Board Column Configuration Missing Statuses

Summary

The JIRA Agile column configuration screen does not properly identify the statuses which belong to the board when the conditions below are met:

1. There is an issue type using a custom workflow, with different statuses.
2. The JQL filter used by the Board references the issue type above.
   • e.g. Using the filter 'project = P AND issuetype = custom_type OR project = P' will cause this problem, even though it should return the same results as the filter 'project = P'.

Moving any of the status for issue types other than custom_type to the 'Unmapped statuses' column will make them disappear from the column configuration screen.

Update: the issue type that uses the custom workflow does not need to be referenced by the filter query in order to cause the problem.

Steps to Reproduce

1. Associate a custom workflow with an issue type in your project
2. Modify the filter of the board to something like project = project AND ("custom_field" = a OR issuetype = issue_type) ORDER BY Rank ASC
3. Create an issue with issue type that uses the custom workflow you associated with
4. Go to board settings -> columns

Expected results

All statuses from all workflows associated to the issue types retrieved in the board will be displayed as options to be mapped.

Actual results

The statuses that belong to the custom workflow will not be displayed. By consequence, the issues associated to the issue type that is using the custom workflow will not appear in the board either.

If you modify the filter to match with a criteria that matches the ones that can cause such problem after all statuses were correctly displayed, you will see the statuses of the custom workflow marked as invalid in the columns's settings:

Workaround

Using the sample filter above - 'project = P AND issuetype = custom_type OR project = P' - and changing it to 'project = P AND issuetype = custom_type OR project = P and issuetype in (standardIssueTypes(),subTaskIssueTypes())', which yields the same results seems to resolve the problem.

Another possibility in case you are using something like project = project AND ("custom_field" = a OR issuetype = issue_type), would be to change that query to (project = project AND ("custom_field" = a OR issuetype = issue_type)) OR (project = project AND ("custom_field" = a AND issuetype != issue_type))