Custom workflow statuses are unavailable when Agile Board filter includes a "text ~" clause

When configuring an agile board with a project that has a custom workflow, the statuses in the workflow are available to be located into columns as desired by the user. However, if the agile board's filter is updated to use a "text ~" clause, valid statuses within the filtered results are no longer available and may not be mapped into columns. Instead, the column configuration appears to revert back to statuses from the default greenhopper workflow, even when those statuses are not part of the project's workflow.

If the columns are configured with the right statuses prior to adding the "text ~" clause, the issues will appear properly within the columns. However once the clause is added, in column configuration the yellow triangle warning symbol will appear along with an indication that the status is not available despite a non-zero count.