Issues in TMP not showing in board and backlog

Question

Background info:

We migrated last year from on premises into the cloud.

All of our projects became CMP.

Now we migrated one of these projects to TMP by creating a new TMP and moving all the issues.

Problem:

A bunch of issues neither show in the board nor the backlog. But they are visible in the "Issues" list.

When I create a new issue (either via "Create" button in top menu bar or directly within the backlog view, the issue is created, I get a brief message that it will not be visible because it doesnt match my project or filters.

The new issue is not visible in the board or backlog, no matter if a transition it to all my workflow's statuses. It never shows.

Now for the fun part:

When I disable the backlog feature, the newly created issue shows up in the board. And when I reenable the backlog feature, it also appears in the backlog view.

And any new issue created afted this "workaround" stays invisible again.

Since the filters for backlogs and boards cannot by customized in TMP I am clueless what is the cause for this problem.

Any ideas?

unknown · Answer

I am aware of the split list in the backlog view and its functionality towards visibility of issues in the board view.

I am also aware that Subtasks are not shown in the backlog view and I know about the custom filters.

As I described in my original post, the problem is not issues that are visible in the backlog view and not visible in the board view, like you assumed in your last message.

The newly created issues of the type "Story" is neither visible in the backlog view (in neither of the two lists and with no existing custom filter) nor is it visible in the board view. In that situation the initial status was not assigned to a board column and so in that state the system works as intended. But when I transition this issue to any of the status assigned the boards columns, the ticket still stays invisible in both views: board and backlog). And yes, I refreshed the views.

When I disable the backlog, the ticket immediate appears in the board. When I then enable the backlog again the issue also appears in the backlog view.

---

Since we disabled the backlog view for good and now use a board with all status assigned to columns, including the initial status, I cannot reproduce the behaviour. And I dont want to mess with that project again since the team is already frustrated about that "incedent".

If we run into this problem again I will pick up on the conversation and maybe do a screen recording to demonstrate it. But for the time being I would declare it some phenomenon we should keep in the back of our minds.

Thank you again for your support!

Trudy P Claspill · Answer

On the Backlog screen there are two lists of issues; one above the other. The top list is labeled "Board" and the bottom list is labeled "Backlog".

All issues that display on the Board view should also display on the Backlog screen in the "Board" list with the following exceptions:

1. Subtasks do not display in the Backlog screen.

2. If you have a Custom/Quick Filter enabled, that may hide issues.

Can you provide screen images of the Board view and the Backlog screen pointing out an issue you can see on the Board that is not displayed on the Backlog screen?

unknown · Answer

Thank you for your anwer Trudy!

Yes, it is a kanban board.

Issues in the initial status were not assigned to any column in our board. And I am aware that these would not be shown in the board. That they will not appear in the backlog is a new information. I keep that in mind.

But the problem is still not solved:
When I transition a newly created issue into a status that is assigned to a column I would expect that issue to appear on the board and in the backlog. But it doesn't.

We helped ourselves now by disabling the backlog view and creating a new column in our board which we named "backlog" and assigned the initial status to. Works ok since that project has a rather small backlog.

I suspect that the problem has to do with the issues coming from a migrated CMP.  It seems to work fine with TMPs we start from scratch. Therefore I recommended to all our other company teams NOT to use TMP on "migrated issues".