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,558,992
Community Members
 
Community Events
184
Community Groups

Jira Issue Ageing Issue based on Ticket updated date

Hi,

Currently to get the number of date between the current date and the jira ticket updated date. we are doing it manually by extracting the issues in excel and then arrive the number of date between the update date and the current date and based on the number of date arrived, put the number of issues under different period buckets viz., within 1 week, 1 to 4 weeks, 4 to 8 weeks, 8 to 12 weeks and so on.  This data is needed at the Jira status level. Is there any way to get this details based on JQL?  The output should be two dimensional - Status wise and week wise

 

1 comment

Rudy Holtkamp
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 28, 2020

Hi, you could use JQL filters for it, but on a dashboard you need several gadgets. For every bucket you need one gadget. Otherwise you should invest in an app that supports your use case. A good candidate would be Custom charts for Jira reports

within 1 week: updated >= -7d order by updated desc

between 1-2 weeks: updated <= -1w and updated >= -4w order by updated desc

And the rest is obvious, I hope.

Tip if you use Kanban/Scrum board, you could use swimlanes to represent the same buckets. Or use quick filters to quickly get these tickets in view. 

Comment

Log in or Sign up to comment