Hi,
My JSD workflow is having multiple statuses like Open/Assigned/Waiting for customer/In Development/Resolved etc
I want to check for how much duration a ticket has been stayed in each status during its life cycle from Creation to Resolved.
Ex : Suppose Ticket CCNS-12345 was created on 01 Sep and resolved on 25 Sep. How to find for how many hours it was in Opended staus, 'Waiting for customer' Status, 'In Development' etc.
Suggestion regarding this are welcome.
Thanks
Vivek
If you simply want to occasionally look at this info you can look at the history info. If you want to monitor or report on this use an addon like Ravi mentioned.
Adding 1 more query to it... Is it possible to check for how much duration a ticket has been stayed in each team (L1 and L2)?
We have 2 assignment groups; 1 for L1 and another for L2. Say : India L1 Team, India L2 Team.
Suppose L1 team deals with ticket on 1st Sep and transfers the ticket to L2 team on 5th. So we need Assigned date of both teams for that Tickets via query.
Assigned to L1 : 1st Sep.
Assigned to L2 : 5th Sep.
Really appreciates your help in this regard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @vivek jain
With Time in Status for Jira Cloud is possible to check for how much duration a ticket has been stayed in each team (as you wrote L1 and L2 team) and in each status. You can do it by creating users groups in column manager at the report Assignee Time.
Also, this app can help you to group statuses of workflow on one column.
Beside it, you can view data as a chart and export reports.
Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your kind reply.
Adding 1 more query to it... Is it possible to check for how much duration a ticket has been stayed in each team? We have 2 assignment groups; 1 for and another for L2.
We want to calculate how much it stayed with L1 Team and how much time with L2 Team.
Really appreciates your help in this regard.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @vivek jain
How do you define "Staying with team"? based on assignee's role?
In any case the history has timestamp of all the changes but to have a report on it you would need the addon time in status or issue history collector.
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply.
As I mentioned we have 2 assignment groups; 1 for L1 and another for L2. Say : India L1 Team, India L2 Team.
Suppose L1 team deals with ticket on 1st Sep and transfers the ticket to L2 team on 5th. So we need Assigned date of both teams for that Tickets via query.
Assigned to L1 : 1st Sep.
Assigned to L2 : 5th Sep.
Hope it clarifies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @vivek jain ,
getting timestamps for historical values is supported by Jira Workflow Toolbox, via the function fieldChangeTimes, e.g.
Example: fieldChangeTimes(%{00017}, ^0% not in ["Critical", "High"] AND ^1% in ["Critical", "High"])
returns the list of timestamps when current issue's priority (field code %{00017}
) has become Critical or High.
Besides this, a function for your initial question is present as well via timeInStatus, e.g.
Example: timeInStatus("Open")
returns the number of milliseconds the current issue has stayed in status "Open".
Cheers
Thorsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.