I am using a Kanban board for a particular team. The backlog column is so long that it is really difficult to go through the whole list if there is a need. (600+ tickets) Anyways to optimize the backlog column from being so "taller" ?
Well other than growing the team to knock the list down 😉
you could consider excluding issues that are considered “deep backlog” or “parking lot”. Let’s say your situation is that you have a lot of issues that are old or otherwise very low priority. If this is the case scrub your backlog and using some tagging method (labels, component or custom field) method, tag this items that you want to hide from the main backlog. Then edit your board filter to exclude the issues. Create a different board if you wish to capture only the parking lot items and schedule regular scrubbing exercises to either close, remove the tagging or leave for now.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
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