Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,779
Community Members
 
Community Events
176
Community Groups

What would be best practice to handle large number of tickets?

Hi All,

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?

 

Thanks,

M

2 answers

1 vote
Chase Wilson Atlassian Team May 10, 2021

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!

0 votes
Capi _resolution_ Marketplace Partner May 21, 2021

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?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events