Ok I see a few different places Jira offers 'Time in Status' and also JQL things about 'updatedBy' to see who last changed it. My head is swimming with query lingo and I'm not sure if I've confused myself to not see the forest through the trees or if this truly is as complicated as I think it is right now.
Our current workflow also has people only assign work while they are actually working on the task. This means I can only associate an assignee during the In Progress status, but I need historical across the lifespan of a project.
My challenge -
How to create & track in a JQL filter,
I believe with these answers I could figure out for a dashboard,
Hi @Bud Herz
Yes, if you haven`t enough time to build automation rules or REST API, you can try apps from the Atlassian marketplace. For example, my team SaaSJet developed the list of apps that can help you:
I hope you will find the best solutions for your needs.
Regards
@Zoryana Bohutska _SaaSJet_ thanks again for these links. I'm working with Time In Status for the weekend. It looks like it's just what the doctor ordered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Bud Herz ,
For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. It is available for Jira Server, Cloud and Data Center.
Time in Status mainly allows you to see how much time each issue spent on each status or assigned to each assignee. You can combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time. You can calculate averages and sums of those durations and counts grouped by issue fields you select. (For example see the total InProgress time per Epic, or average number of InProgress transitions per issuetype).
Something particularly useful for you is the Status by Assignee and Assignee by Status reports. These reports show status times broken down to assignees or assignee times broken down to statuses.
Time in Status can display all its reports and charts in it own reporting page, in dashboard gadgets and in a tab on issue view screens. Below are some samples:
The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.
Using Time in Status you can:
https://marketplace.atlassian.com/1211756
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Emre, but I am already working with a different Time in Status tool - https://marketplace.atlassian.com/apps/1219732/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bud Herz ,
As an alternative, you can try Status Time app developed by our team at Bloompeak. It provides reports on how much time passed in each status as well as status entry dates and status transition count.
Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project). And all these are available as gadgets on the dashboard too.
Here is the online demo link, you can see it in action and try.
If you are looking for a free solution, you can try the limited version Status Time Free. 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.
Hi @Bud Herz
Sorry to be the bearer of unhelpful news...For the good questions you are asking, most of the information is in the change logs for issues. However with out-of-the-box Jira features that info cannot be easily queried. There are marketplace add-ons for JQL, status analysis, and dashboards which make such investigation easier.
For non-purchase options, you can build some reporting yourself using custom fields and automation rules, or by calling the REST API. For example, recording and preserving who moved issues into progress, how long they were there, etc. Even after doing that, you might need dashboard add-ons to adequately report the data.
Best regards,
Bill
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.