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. The yellow triangle icon states "This status is not available in any of the workflows used by this board"

This is similar to JSWSERVER-11623, rather the customer issue for this bug was resolved via referencing the same. Opening this bug to track the issue for cloud .

Steps to Reproduce:

*Refer the steps in https://jira.atlassian.com/browse/JSWSERVER-11623*

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())

In customer's case the filter was : project = GI AND ("Epic Link" = GI-2 OR issuekey = GI-2) ORDER BY Rank ASC . The statuses were in warning for filter Epic Link = GI-2** and issuekey = GI-2 ** statuses were without any warning. T

The issue was resolved after changing the filter to project = GI AND ("Epic Link" = GI-2 OR issuekey = GI-2) and issuetype in (standardIssueTypes(),subTaskIssueTypes()) ORDER BY Rank ASC