how can I see more columns in backlogs?
What do you want from a column in a backlog? A backlog is a list of issues to be prioritised and then drawn into a sprint, or a list of stuff that needs doing (Which, once you've started to look at it, by definition, isn't backlog any more)
Hello everyone,
We understand the necessity of some teams to have more columns/fields in the backlog as a better way to filter/prioritize issues before adding them to the Sprint, and that's why we created the following suggestion to get all our customers feedback and ideas to make this feature better:
Ability to re-order the backlog from Issue Navigator using Drag and Drop.
On the other hand, the action of simply adding new columns to the backlog view might add more complexity to a feature intended to simply list the items scheduled for the next Sprint. This would cause more confusion for the teams that use that feature as it was intended to work, and break the whole Scrum methodology that should be applied to a short-term backlog.
That being said, we have Advanced Roadmaps for Jira Cloud support as an option today that can help with the planning of a long-term backlog and might work well for most of the scenarios provided in this thread. Feel free to take a look and check if that option works for your team!
Also, feel free to vote/watch and give your feedback on the suggestion mentioned above, as that is our direct channel to contact the product managers of Jira applications.
Best Regards,
Petter Gonçalves - Atlassian Support
Perhaps they are looking for useful information to help them prioritize items like story points or business value.
I am also wanting to know how to do this. I need it to help prioritize / categorize the tasks in the backlog.
I would love to see which issues are in which state of the workflow. It would be awesome to see if something is in progress (rolled over from the previous sprint) and if something is blocked.
Although adding columns to the Backlog view is something I'm also looking for, I think you need to be careful which columns you believe are needed. Up above a user asked for the State (or Status in Jira language). The fundamental problem with this is nothing in the Backlog should have an associated Status with it because it hasn't been assigned to a sprint, so why is somebody working on it.
Having said that, I would like to see the status in the scenario when a developer sees a related bug in the Backlog and fixes it even though it hasn't been assigned to a sprint. I need a visual clue that the bug should be moved into the sprint so it can be verified. It breaks the rules of scrum a little, but is a very realistic situation.
I see your point, but for us the backlog view contains the backlog + all planned sprints for the year.
KAM:s and Sales people can come to me for a high level estimate and a planned delivery. I plan it for a sprint five months from now. Any person involved in the business side of things, will know that they have gotten an initial OK from the product organization. But before any scrum team will develop, the requirements will have to be accepted by the PO and Scrum Master. Until the requirements are accepted, no development team will touch your case.
Right now, we have zero visibility. Sure, I can create seperate dashboards for people, but it's hard enough to get people to just log into Jira. We have maybe 100 people that, from time to time, are interested in their case. They have no idea what the case number is, nor do they have any interest or knowledga about sprints, Jira or anything like that. The routine to follow up their case should be simple:
1) Log in to Jira
2) Look in the backlog
3) If it's not planned - we won't do it.
4) If requirements are not accepted by the team - we won't do it.
The reason for status is before an item can be added into a sprint it needs to be in Ready for Development. The status for us prior to that is Needs Information and Ready to Refine. Then once an item is in the sprint you can see the status on the "Active Sprint" screen, but you then can not see the priority. With multiple developers, sometime the highest priority takes longer, so its nice to use the backlog view to see priority and status.
Any outcome on this? I have exactly the same circumstance as described, and simply looking to add some columns in the view - there's a lot of real estate wasted here!
I have the same request.
Why is this accepted? We'd also like to see the status in the Backlog to know which items still need further refinement (specification) and which are ready to be drawn into a sprint (even if they do not have a high priority).
It's accepted because the answer (and/or its comments) are a good explanation of the current way things work, and why.
Jiras design for the backlog list indicates that Atlassian knows very well that you need an overview of the backlog AND the sprints, in order to plan and visualize the backlog.
But you're telling me that we don't need any information to plan? And if we need information, all companies, teams and processes need the same information?
@Nic Brough -Adaptavist-the only answer was yours "What do you want from a column in a backlog?"
This is not an answer. I'll try to clarify the request: When you click on an issue in a backlog, the right panel shows all the details from that issue. That panel only exists because sometimes it's important to see details of an issue in a backlog.
Now, imagine you want to see details of several issues at once, to help you prioritize them. This is what columns in list views are for.
Why is this still not fixed? 2021 and I need to add columns to backlog so I can see if the work in preparing a ticket is done before we can allocate these to a sprint.
In non trivial projects, there are lots of work to do on backlogs before you can allocate them to sprint!
Jira is too big to fail? doesnt listen to people doing the work?
There is nothing to "fix" here. The problems people think would be ameleorated by botching columns in won't be.
You said yourself "A backlog is a list of issues to be prioritised and then drawn into a sprint"
The decisions of which items to draw will depend on what stage of preparation they are at. Design, Allocate,Estimate,Review,Ready For Sprint. So if you see 200 backlog tickets there is no way to know which ones are Ready For Sprint. If you added a column for status, we would know!
Please post the alternative solution for this if there is one.
The alternative is to ignore this pointless backlog screen, and use Issue Navigator to see those details. Unfortunately we can't re-order items in Issue Navigator - see https://jira.atlassian.com/browse/JRACLOUD-75060
Dear Petter,
I believe most of us know what they want to achieve and plan to add just a few columns that are really needed.
We for example would need an additional column to support the planning with our departments: when requirements are not specified clearly, we still need a rough estimate and would use a separate field for that to be shown in the backlog.
It looks like you're new here. Sign in or register to get started.
