Filter that shows issues assigned to me AND on the Board (if Kanban) or in Sprint (if Scrum)

Question

Hello all,

I’m trying to create a dashboard to see all my current stories accros all projects.

Some are using Kanban and some Scrum but in any case I only want to show the issues (regardless of the issue type) that are assigned to be and that are « active » (i.e. are on a board).

In other words, I don’t want to see any issues from the backlogs

Thanks a lot!

Trudy P Claspill · Answer

Are you using a Team Managed project Kanban board?

There is currently no way to filter for an issue on a Team Managed Kanban board distinguishing between the issue being in the backlog or on the board.

I've seen post where other people use another field to help them determine that distinction, like adding a label to issues that in the backlog and removing that label when an issue is moved to the board, or making sure that the issues are Assigned to somebody when they are moved to the board, and always remain assigned while on the board, and are never Assigned when in the backlog.

Benjamin Charbit · Answer

Thanks Mikael.

That's what I thought but the issue is that I have issues with status "To Do" both in the backlog AND on the Kanban board.

In my company, we move things we want to work on next on the Kanban board. So I only want to see these.

Trudy P Claspill · Answer

It might work if you create a filter that uses StatusCategory.

Every status is assigned to one of these Status Categories:

- To Do

- In Progress

- Done

Your filter would be

assignee=currentuser() and StatusCategory in (In Progress, Done)

However, this depends somewhat on how your Kanban boards are set up, and proper use of Statuses in Scrum boards.

If you have work on Kanban boards that don't use a Backlog, the issues assigned to you that are in a "To Do" status would actually be "on the board".

If you have work in a Kanban board where there is more than one status for the To Do StatusCategory, and they are not all mapped to the Backlog screen for that Kanban board, then that could possible exclude issues from your results.

If there is a chance that you have an issue that is part of a Scrum board where the issue has not been added to a Sprint but the issue status has been changed to In Progress (which would not really be proper) then those would be included in your results though they would not actually be displayed "on the board".