Why do items in Next Gen backlogs have a status from the board not the status Backlog?

[Deleted user]

It's really annoying when we search or build confluence reports from issues in a Next Gen board that we can't actually distinguish those things in the backlog (we turned on the backlog feature). We had to build a backlog column on the board and not put anything in it. Really weird. Can someone explain the logic behind this limitation??

[Łukasz Modzelewski _Transition Technologies PSC_]

When you have same number of columns and statuses then its simple as 1 to 1, but when you add more statuses, then those need to be placed in some column. 

https://support.atlassian.com/jira-software-cloud/docs/manage-columns-with-multiple-statuses-in-a-team-managed-project/ 

Columns on board are for visualisation, and placement in some segment. If you look at single issue (not from the board view) then it's status is more important then kanban column, as it is not reachable/visible from that view