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
So within our Jira, we have multiple Team managed projects which are our customers (we have multiple request types that are for support tickets, asset repairs and such)
Now, what is required is a report or dashboard to display this
Which assignee group -> assignee and if they initiated a "clock-stop" which is when the SLA counter is paused, we are in need of a way that can dynamically go through projects or parameters to do then show currently all clock-stopped by who and their member group
We have EasyBi, but doesn't seem to be able to display in this way.
What I tried to do is use status time to make a report, but this isn't what I need. I want to know if paused and who paused and how long this pause is running. Is this possible to go about in a standard way? with EasyBi or this plugin
Hi, @Kameel Naidoo
I appreciate your interest in the eazyBI.
We are importing Issue change history data in the eazyBI; please read more here: https://docs.eazybi.com/eazybi/data-import/data-from-jira/import-issue-change-history
In this case, if you have a Statuss assigned to the Paused in the Jira SLA configuration, you can use measures: Days in transition status, Transition Author, Days in transition, Transition to Status, and Transition From status to report the Paused status.
For example, I have the "Waiting for customer" set as Paused.
Let's take the issue IP-11 as an example.
Measure, "Days in transition", shows the time spent in this status. You can see that Sandra Adams paused the issue, and Adam Mint unpaused it. The issue was on pause for 0.001065 days.
Measure, "Days in transition", is based on "Transition from status". All the paused time will be shown under the user who unpauses the issue.
Please, if you need support or you are stuck with the report building in eazyBI, don't hesitate to ask our support team: firstname.lastname@example.org
Hi @Kameel Naidoo ,
I spent some time here and, while I am not a JSM expert, I am not seeing a way to query and display the information you are desiring.
How are you stopping the SLA clock?
In general, there are three ways to pause an SLA clock, and they are generally based on conditions rather than a user clicking "stop clock": https://confluence.atlassian.com/jirakb/understanding-why-an-sla-is-paused-in-a-jira-service-management-ticket-1271267987.html
Here is a reference which covers common SLQ queries:
Yet none of the queries covers how to evaluate which user paused a clock.
Perhaps you could run a JQL query to display "paused()" issues and then, in the list of results, use the assignee as the one who last updated the ticket?
Yet the assignee may not be the one who updated the ticket... While the standard columns to view search results does not have a column for "last updated by", JQL does have an "updatedBy()" function.
Hopefully this helps, or at least gets you pointed in the right direction.
So "Stop-Clock" is more an internal term we have become used to, but basically what is occurring is in Transitions there is one called clock-stop and in the SLA config it is set to pause in that status. In this plugin I am then collating both clock-stop transitions to the 1 count column, so I think it would make a good addition for reporting purposes. But seemingly the only way to do this to exact spec is to query the API and pull data, then do the appropriate calculative measures and create a view outside jira or in turn then supply that to EasyBi or such, lot's of hoops for something that should be part of the calculative reporting
I agree - that's good data to collect. I think you're just ahead of the crowd with what you're gathering.
When you have a system in place, be sure to post the details here and mark this ticket as answered so that others can benefit from what you are doing.