Status from workflows not associated with issues on board are appearing in Configuration

[mike]

In board configuration -> configure columns, there are far more statuses available than the issues my filter captures are able to use.

These "extra status" are associated with workflows that none of the projects in my board are using.

I am sure my board filter is not capturing any task from any project that is using the workflow for which these statuses are associated with.

I have checked every workflow for every project the board filter captures and none of these "extra statuses" are appearing anywhere on them.  I'm also checking the workflow scheme via the admin page.

How does Agile decide what statuses are available on the Columns configuration page?  I know I can simply unmap them, but I'm more curious in how they showed up in the first place.

I'll try an example:

Board filter: project in (A,B,C)

A workflow: wA.  B workflow: wB, etc...

wA statuses:
Open, Working, Test, Resolved, Closed

wB statuses:
Open, In Work, Review, Resolved, Closed

etc...

Extra statuses:
ToDo, Working, Missing, etc....

None of these statuses associated with the other projects or workflows or schemes. Yet there they are available for sorting into columns.

[Nic Brough -Adaptavist- · Accepted solution]

If you create the board with a filter that's a bit too complex or open, it can give up and just show you every single status there is on the list.  And, annoyingly, you can't get rid of them easily, even by correcting the filter to narrow it down to the project/issue-type you actually care about.

I've never worked out an exact pattern for when it does this, or how to fix it by doing anything other than creating a new board from a saved filter that has only the project/issue-type correctly selected before I go to the board.

[mike]

So it's basically a glitch? Thought as much. It doesn't really stop me from doing things so it's not too big a deal.

Thanks for reply.