Stories with Backlog status have disappeared from the Backlog view, even though no filters are active. The stories are still visible in the List view with the correct Backlog status, but they don't appear in the Backlog navigation. What could cause this?
Check the configuration of the board.
Is the backlog option still enabled and the status mapped to the backlog, for company managed space, or is the status mapped to the backlog on Team managed space?
Thanks for the answer @Marc -Devoteam-
It's Team-Managed space and the status is mapped to the backlog. The interesting part here is that under the Backlog it's also showing 0 work items
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Resolved!
The issue was in the Workflow configuration, the Backlog status had its category set to "Done" instead of "To Do".
Not sure how or when this changed, but switching the category back to "To Do" fixed everything.
Thanks everyone for the suggestions — especially pointing me toward the workflow and board configuration. Really appreciate the help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alla Tadevosyan jan,
Happy to hear that the issue is resolved :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alla Tadevosyan,
Welcome to Atlassian Community!
Boards are controlled by a filter, so that is what I would look at first. Does the filter return those items that are in the backlog status?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mikael Sandberg ,
Thanks for warm welcome!
Actually yes, the filer search shows the backlog items as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alla Tadevosyan jan,
Since you confirmed that the filter and backlog mapping are correct, this doesn't sound like a configuration issue. I'd try refreshing the board configuration by temporarily removing and re-adding the backlog status, and, if the problem persists, I'd recommend opening a support ticket with Atlassian, as this may be a product issue rather than a configuration problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the warm welcome and detailed instructions Gor jan,
I'll try this way. If the issue isn't resolved by refreshing the configurations, I will raise a ticket accordingly!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alla Tadevosyan jan, happy to help! 😊
Please let us know if refreshing the board resolves the issue.
If it does, we'd appreciate it if you could mark the answer that helped as Accepted, so it can also help other community members who encounter the same problem in the future.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not refreshing the board itself, but it definitely helped to dive deeper!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alla Tadevosyan
Welcome to the Atlassian Community!
Both @Marc -Devoteam- and @Mikael Sandberg suggestions are good starting points.
I'd first verify the board filter and the backlog/status mapping, as those are the most common reasons for issues disappearing from the Backlog while remaining visible elsewhere. Also check the board filter; does it return that issue?
I'd also check whether the affected issues have accidentally been assigned to an active sprint. Work items that belong to an active sprint won't appear in the Backlog, even though they are still returned by the board filter and visible in the List view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.