Hi, trying to run a basic gadget / dashboard showing # of issues at 0-30 days old, 31-60, >60.
Have tried the standard gadgets and fields, but none do this pretty common and basic function.
Tried custom issue field "Days since Creation" (Text and number formats) and used automation script to run daily:
{{issue.created.diff(now)}} This works but places it as a complex text string and will not add it as a number (of days) in the number formatted field at all. Filters cannot use this format in terms of "days" calculations either.
Likewise filter scripts seem to be oriented at time in terms of looking back from now vs counting from creation.
How can this be done?
Hi @Marc Parsons -- Welcome to the Atlassian Community!
What do you mean by:
{{issue.created.diff(now)}} This works but places it as a complex text string and will not add it as a number (of days) in the number formatted field at all.
To get the number of days difference between created and now in an automation rule, remember to include the units of measure for days. This will allow storing the result in a custom, number field.
{{issue.created.diff(now).days}}
Kind regards,
Bill
welcome to the community!
I trust that you'll be able to solve this using Jira Automation based on Bill's great answer.
Just for future reference: If you're open to solutions from the Atlassian Marketplace, you'll have more options available. E.g., I believe that your use case could be easy to solve using the app that my team and I are working on: JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called history columns that aren’t natively available, including the time since issue creation.
This is how it looks in action:
As you can see above, you can easily sort and filter by the time since issue creation, and also use it across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting. You also have full control over the format in which it is displayed; I'm using days in the example above.
This all just works - there's no scripting or automation whatsoever required.
Any questions just let me know,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.