I have a project with a Kanban Backlog, which shows `Backlog` items, and `Selected for Development` items. These are both driven by the status of an issue.
We have a status that lives between backlog and selected for development. The project is for externals and we have a status called `Refinement` which is like a backlog item, but it has been populated with all the relevant information and is for the developers to review that it can be worked on, once this is agreed, we can move it into Selected.
Currently we can toggle a filter on/off for tickets in refinement status, however if we could have another sprint-like section between backlog and selected, this would be great. Anyone know if it is possible?
Image above has 2 sprint like sections, I am trying to add a 3rd that sits between the two.
You should go to the Board Settings -> Columns and add a new column. Then you should map a status to the column. You can find more info here:
Thanks again Alexey for taking the time to respond.
I'm not talking about columns, I know backlog doesn't have columns.
However, in Kanban backlog mode, you have the backlog with two sections that look a lot like sprints if you are using scrum mode.
These two "sprint-like" sections are driven from the 2 status types `Backlog` and `Selected for development`. I was wondering if it was possible to add a third sprint-like section in between, driven by a status preferably but other means would be fine.
I hope my request is a little more clear now.
I hope to bring more light to this question. We'd like to have the same thing. I had hoped to solve it by putting 3 statuses in the 'kanban backlog' section of the board config. I thought this might create a 3rd-horizontal-section on the backlog, with the name of the status, in the order it appeared in the 'kanban backlog' config.
@Zachary_Jones, that is not an option in the backlog. There are other solutions discussed in other threads so you might want to search a bit. For example some people create a different Kanban for their “deep backlog”. They use that board as a first filter moving stuff ready to be considered for dev to the other board.
We would need this as well! The problem with the regular board is, for example, that when you move one story with visible subtasks to another column, then the subtasks remain there. However, in the backlog you have the possibility to move a story with all its subtask to another status.
Same problem here.
It's hard to priorize a big number of tasks in the Kanban View because of the size of each element. Backlog view is much better when we need to see a huge number of tasks.
In our case, we have 4 status "Open, Qualified, In Conception, Ready to Dev" and we need to priorize these 4 tasks groups and their tasks. It would be very nice to have a "custom backlog view" with as much group of tasks as necessary (and to be able to also see them in kanban in the same order)
@Mitch Kent, I did something a few years back that was similar to what you are speaking of however ultimately I found it too cumbersome.
Basically, I had a rather complex workflow with two main focuses and two boards. The first covered statuses that applied to the Product Management team and the second with Development. The PM team would guide the issues thru the assessment and requirements stage and then finally land them in Selected for Development (right most column). The Dev board began with this status so it was the Backlog. Then the Dev team would basically select from the Backlog and place into the sprint.
In summary you could easily use another status, label, custom field and use that to exclude issues into a refinement Backlog and manage with two boards. However, as Alexey conveyed, it can be done on a single board.
What I'm trying to achieve could be done within a single board, hopefully, I was just trying to prevent things from showing up on our board if they are not yet "Ready".
In scrum previously this was achieved by creating a sprint or two back in the backlog, BA/PM/PO could put the tickets in those psuedo-sprints, and dev team would be refining those tickets prior to sprint start. I want to replicate this by having a backlog that we can see what tickets are candidates for "selected for development" but without polluting our kanban board.
The only way I know how is, as you point out, filtering based on status (or label/field) but it would be nice if there was a permanent visual way of displaying these in the backlog view.
In Kanban world (as it exists today) you are not going to be able to create another 'section' in the backlog. Scrum is obviously different and does allow you that level of planning by using multiple sprints in the backlog view.
With Kanban if you want it on a single board then you could simply use a label, something like this:
Messy, and I wouldn't go there personally but that would be a single board solution. Personally, I would opt for two board solution unless my 'deep backlog' needs were few. My two board solution would actually be a status called NMI (need more info), exclude NMI from the Dev board and have the other board be only NMI. When i'm ready I transition an issue from NMI to ToDo.
Thanks Jack - it was a hopeful request, rather than an expectant one :)
I will likely do as you suggest, but with a quick filter based on status type in backlog view - this was always my backup plan. Alternatively I may create a column for it in our board so that it means we're aware of it, but I'll discuss that with my team first - it's still early days so we'll work it out as we go :)
No idea why this isn't a thing yet. You can do this with SCRUM boards by creating multiple sprints and dropping the issues into the corresponding areas. Why on earth is this functionality not extrapolated for Kanbans. I have three different statuses that do not need to be appearing on the board yet, but I do want to arrange them in the backlog view.
We'd really like this feature. I know may not be considered "pure" kanban, but it's how we want to work.
We have a huge backlog, and we'd like to keep our "future work" separated from what we're considering doing next in a way that is easier to do than just moving individual stories up and down in the backlog itself. Sort of like "on deck" work, as opposed to future - it still needs some details/grooming, but it's the basic idea of what the devs want to do next.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events