I'm just curious, what would be the best practice to handle a large number of tickets in Jira Work Management?
For example in Jira Software using scrum board I can put not active tickets in the backlog and then break them down into multiple sprints. That helps to manage those tasks and plan accordingly.
So, what if I have 500 tickets using Jira Work Management in "To Do" column, and I keep adding them based on the client's needs? As for now, from what I can see, the only solution is to store them in "To Do" column and define "Due Date", so they can be displayed on the Timeline or in the Calendar.
Do you have any thoughts or plans to add new features to the product?
Hi @Max Sudik , thanks for the question. For larger projects, I would use the List view primarily and take advantage of the new filtering options. This should make it easier to reduce the number of visible tasks to be done. You can also sort by when issues were created, updated, or their priority if any of those options make it easier. Hope that helps!
Interesting question @Max Sudik , but I imagine that there could be as many good practices for sorting 500 tickets as there are organizations and immediate needs.
Would you consider more sophisticated prioritization schemes? Categories and labels? Additional columns?
Welcome to the Jira Work Management FAQ We're glad you're here. If you haven't already, watch our video to get a one-minute overview of Jira Work Management. Check out some basic technical and logi...
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