You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a question about tracking 1500 events with 5 subtasks each. What is the best way to track this amount of events. I want to be able to come in to work in the morning and spend as little time as possible looking at the events from the prior day. I know you can use RoadMaps, Dashboards, JQL Queries, what else can we do? Can anyone suggest the quickest way to get this done every morning? have looked in the Atlassian community and found a lot of answers and I am reaching to ask the rest of the people that are working with Jira. Thanks in advance for the help. https://community.atlassian.com/t5/Jira-Software-questions/Tracking-tasks-and-subtasks-individually-whilst-linked-to-a/qaq-p/1730181
@David Theroux can you share a bit more about what you're trying to do?
I have a hard time believing any individual user is expected to actively watch 7500 tickets at a given time when nothing changes on 95% of them for weeks. You could do a simple filter where you look at updates/changes so you review the 'only' 375 that changed since the last time you checked?
Hello Matt, I am a Jira sys admin and I have already suggested what you are saying. I think the quickest way to go on this would be the JQL query/Filter. That's what my customer has asked for...What he is trying to do is what I mentioned in the first que. Wants to monitor 1500 tasks and some have 5 sub tasks. Wants to know the quickest way to go through issues that have changed. I just wanted to make sure I covered all the bases before I give my customer a definitive answer. Thanks for your input Matt, We appreciate you sir!
@David Theroux understood, that makes much more sense.
I would recommend adding something like the following to your existing JQL:
updated >= startofWeek(-1)
As it reads, this will show any tickets that were updated since last week. You can also use startofDay, startofMonth, startofYear, etc. You can see additional details here: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#Advancedsearchingfunctionsreference-startOfDay
The 'updated' field is a system field that is changed whenever any changes are made to the respective ticket. Depending on how your customer views 'changed since' that will define the specific function you use.