and resolved <
and resolved <
Find issues where Time to First Response was breached:
"Time to First Response" = everBreached()
Find issues where the SLA for Time to Resolution is paused due to a condition:
"Time to Resolution" = paused()
Find issues where the SLA for Time to Resolution is paused due to the SLA calendar:
"Time to Resolution" = withinCalendarHours()
Find issues that have been waiting for a response for more than 1 hour:
"Time to First Response" > elapsed("1h")
Find issues that that will breach Time to First Response in the next two hours:
"Time to First Response" < remaining("2h")
Created and updated are system fields that are calculated for you.
"Date closed" cannot be, as Jira does not know what you might consider to be the date an issue was closed - that depends on your process and workflow.
If you want to see your version of closed date, you'll need to capture it as part of your workflow, then you'll be able to include and show it in reports.
The other option is to work with Jira's default assumption of when an issue is closed, which Sachin mentioned already. That is "whenever the resolution last changed to a value other than null". This is captured in the field called simply resolved , so if that measure would work, try adding that to the reporting.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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