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, AND
2. The JQL filter used by the Board references the issue type above, OR
   • 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'.
3. The JQL filter used by the board reference to text
   • e.g Using the filter project = P AND text ~ "testtext"

The problem happens when the project/board is configured in such a way that it has multiple workflows (for different issue types). The board seems to only consider the statuses from the first workflow listed under its workflow scheme. The other statuses from the rest of workflow in the same workflow scheme will have a warning triangle indicating that the board doesn't recognize them.

Moving any of the status with the warning triangle to the 'Unmapped statuses' column will make them disappear from the column configuration screen.

Steps to Reproduce:

1. Restore the attached XML backup (column_issue.zip).
2. Navigate to Agile > Sample Scrum Project A.
3. Go to Board > Configure.
4. Go to Columns - All statuses are displayed and properly mapped to columns.
5. Go to General and change the 'Working Filter SSPA' to the 'Broken Filter SSPA'.
6. Refresh the Board configuration page for the new filter to be applied.
7. Click on Columns again - The status which do not belong to the workflow used by the issue type "Test Issue Type" will have a warning triangle with the message below:
   "This status is not available in any of the workflows used by this board. To remove, drag it to unmapped statuses where it will no longer be available."
8. Dragging any of those statuses to the Unmapped Statuses column will make the status disappear from the column configuration screen.

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.
• project = P AND text ~ "testtext" is to be changed to project = P AND text ~ "testtext" AND issuetype in (standardIssueTypes(),subTaskIssueTypes())