-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
9
-
Hi,
In next gen projects we can activate a backlog, but we can't filter on issues that are in the backlog.
Status is considered as the same as in your first column
Further information added from other tickets 16 January 2024:
It would be helpful to be able to filter tickets by status in the backlog in the event they're not all in To Do status.
Currently, there is no possible way to differentiate the issues in backlog or board of a nextgen project with Kanban methodology. The status is not sufficed and hence a JQL cannot be used to filter out the issues.
Steps -
1) Use a next gen project in Jira
2) Enable the function "board" and "backlog"
3) Switch to the backlog per navigation
3) Create two issues
4) Move one issue from the lower backlog part to the upper part "board"
5) You can now see one issue being displayed on the board (navigate to board) and one further issue, which is visible in the "backlog" view.
There is no possible way to apply a JQL that can identify the issues in the backlog or board.
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed
[JRACLOUD-87269] Ability to search / filter issues in a team-managed project depending on whether they are on board or backlog
this makes next-gen projects practically useless. Doesn't make sense to show backlog items in the main board
I hit this literally in the first filter I ever wrote in Jira. I was trying to build a multi-project Kanban board that would let me to see the work load of my team all at once. The fact I see everything on our backlog in the "To Do" column makes the multi-project board practically useless.
This sounds like a simple feature and it has been requested for a couple of years already. I'd pretty much like to see it implemented.
The lack of filtering by kanban backlog visibility in team-based projects essentially renders the whole Backlog feature broken by design.
Funny, it works great in Company-managed projects, so not sure what Product Manager on your side came up with this "smart" improvement that makes things worse instead of improving them. Please, this needs to be addressed asap.
Our team started off with a team-managed board, but as we grew our usage of Jira, we wanted to migrate issues on our board but NOT issues from backlog to a company-managed project.
Without this feature it is impossible to migrate issues from team-managed boards to company-managed boards sensibly. I can't even figure out a workaround.
We used to use Sprints, but we found sprints didn't work well for our team. so we switched to kanban which we like a lot more.
And filtering the Backlog view is fine. we an see what is and is not on the board/backlog.
But, in the Issues view, and with JQL, we'd like to be able to filter by whether the issue is on the board or not (like we used to be able to when we used sprints).
We'd also like to be able to see whether the issue is on the board (or backlog) when on the issue page. (and we'd like to move it on or off the board too) as we often look at issues individually and determine whether we want to put it into "view" or not.
We definitely would love to have this. We have a custom Kanban board that we use to view issues from multiple team-managed projects via a custom filter, and we really want that board to only include each project's "board" issues and not the "backlog" issues.
I currently can't see any way to accomplish that goal, and it really makes the combined board less effective.
Note: if moving an issue to the board could set the sprint attribute (even for projects with sprints disabled), then we could use sprint is EMPTY. But if that causes issues with other sprint-related features, then it would be great if there could just be a new attribute for us to query on, like backlogStatus = "board" or backlogStatus = "backlog"
How is the backlog status information not available in JQL?
A few simple use cases that are impossible due to this missing functionality (which I consider a BUG):
This makes it extremely difficult to track ongoing and future work, and impossible to generate automated reports. In other words, I waste a lot of time searching for things in the UI that could be isolated with a trivial JQL query. Developers are human and forget to follow the processes sometimes - I should be able to find these tickets via JQL.
3 years since the ticket was opened and still not even considered! Next-gen Kanban boards are pretty terrible to use if you have more than a few tickets in the backlog. I massively regret moving to next-gen Kanban boards.