Welcome to the Atlassian Community!
There is not really any issue here. I think I need to ask what problem this is causing you?
The Software boards (the ones that have lots of configuration options) are not tied to projects. When you are looking to configure their columns, they do not look at a project, they look at the filter you have told them to use for selecting the issues they are going to work with.
If the filter is limited to a specific set of projects and/or issue types, then the board can look up what workflows are in use on issues it might select in the future, so it can limit the list of available status to the ones used by the workflows, but if you've got a filter that is more inclusive, then it has no choice but to offer you all the status that might be used.
Compare these two board filters:
In the first, your board can get a finite list of status in use in that project, it knows other status won't happen, so in the column mapping screen, it only lists those status. In the second, Bob could be assigned to something in any project Bob is an assignee, and the label xyz could be added to any issue in the system. So every status has to be offered.
But. So what if a board is configured to have status that are not in a project? If you don't have any issues in the status, it won't show anything for that status. The "extra" status has no impact on your view of the board.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events