Comments
-
Hello @Jerome Salaun , For a ready built solution that offers great fexibility and details, our team at OBSS built Timepiece - Time in Status for Jira app. It is available for Jira Server, Cloud and Data Center. Timepiece allows you to see how much time each issue spent on each status. You can combine statuses…
-
Hello @Luiz Felipe Ferreira , Our team at OBSS built Timepiece - Time in Status for Jira app that can meet your needs about dates (and do more) Time in Status mainly shows you how much time each issue spent on each status or assignee. It also has 4 types of date reports showing entry and exit dates for each status. You can…
-
Hello @Johnson Anthony , Since you are asking for an SQL, I presume you are working on Jira Server or Data Center. The changes on an issue (including status changes) are kept in ChangeItemGroup and ChangeItem DB tables. Unfortunately the data in the tables are raw records, more or less the same data you see in the History…
-
Hello, Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need (and more) Using Time in Status you can see how many times each Status or each Transition in the workflow was used. You can get these counts as an issue list or you can have Time in Status calculate sums or averages, grouped by fields…
-
See Andy Heinzer's answer here: https://community.atlassian.com/t5/Jira-questions/Create-Kanban-project-with-sample-data-in-Jira-Cloud/qaq-p/904789
-
Actually, our app Baselines for Confluence does this exact thing. You can use Baselines for Confluence to create snapshots of pages in a space. The app does not save the actual content of pages but rather saves a set of versioned page links, version numbers and locations. You can open a saved baseline to see the page…
-
Hello Sarvesh, Actually, Jira does not care about the status of issues. For Jira, an issue is unresolved as long as the Resolution system field is empty and it is resolved when a value is set for that field. The average age chart (or gadget) shows the average resolution time for the selected issues. For each day in the…
-
Hello @Rhea Mehta , For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit…
-
Hello Chris, Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you can create reports on the dates of each issue status transition. For issues that visit the same status more than once, Time in Status has 4…
-
Time in Status for Jira Server and Data Center editions operate completely on your Jira instance. They do not send any data out.
-
Hello, Time in Status by OBSS works as a separate service on the internet. In order to prepare the requested reports, it pulls data from your Jira instance and does some processing on its servers. The resulting output is then served to your Jira UI. In fact this way of working is not specific to Time in Status. This is how…
-
@Hello @Pooja , The Control Chart which is available in Kanban Board reports, provides a high level solution for such cases. You don't have to create any date fields since all the data you need is already available in Jira issue's histories and Control Chart uses this data. Using the control chart you can select board…
-
Even though your article aims for Jira at the end, for those using Confluence for keeping their requirements, our team at OBSS built Baselines for Confluence app. https://marketplace.atlassian.com/1212963 You know, Confluence already keeps all versions of its pages. This app creates a collection of version specific page…
-
Hello @Kara-Lucia , I wouldn't want to let @Bill Sheboy down so here I am recommending our app for this need :P Our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to…
-
Hello @Ashish Agarwal , Time in Status app by OBSS can be utilized for this purpose (among other things). We prepared a use case documents that explain how to calculate Lead Time, Cycle Time and Throughput using Time in Status by OBSS. You might want to check them out:…
-
Hello @muneet.bakshi , Having all work in a single project is a big "NO NO NO". I suggest you define your projects based on products, not teams. For your current case, the two options might look the same but it is important to make the distinction. I personally define a software product as something that has its own…
-
Hello @Evelyn Dieppa , We recently prepared a use case document that explains how to calculate throughput using Time in Status by OBSS. You might also want to check it out: https://dev.obss.com.tr/confluence/pages/viewpage.action?pageId=303795348 EmreT
-
Hello @Louise Boulton , Time in Status app by OBSS can be utilized for this purpose (among other things). We prepared a new use case document that explains how to calculate throughput for, multiple time periods, using Time in Status by OBSS. You might also want to check it out:…
-
Hello @jean cameron , For simple filtering, you can use a JQL like this one: project = X and NOT (status changed AFTER -7d and status changed BEFORE -1d) If you want to get more data about how long a card stays in a status, Our team at OBSS built Time in Status app for this exact need. The app produces reports much more…
-
Hello @Evelyn Dieppa , We recently prepared a use case document that explains how to calculate throughput using Time in Status by OBSS. You might also want to check it out: https://dev.obss.com.tr/confluence/pages/viewpage.action?pageId=303795348 EmreT
-
Hello @Lusine_Davtyan , Time in Status app by OBSS can be utilized for this purpose (among other things). We prepared a new use case document that explains how to calculate throughput using Time in Status by OBSS. You might also want to check it out: https://dev.obss.com.tr/confluence/pages/viewpage.action?pageId=303795348…
-
Hello @Frank Reveles , We prepared a new use case document that explains how to calculate throughput using Time in Status by OBSS. You might also want to check it out: https://dev.obss.com.tr/confluence/pages/viewpage.action?pageId=303795348 EmreT
-
Hello @Ben Kelly , If you are interested in a ready built solution, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. The app produces reports much more detailed than the control chart and gives you much more control over the reports. It is available for Jira Server, Cloud and Data Center.…
-
Hello @John Charles , If you are interested in a ready built solution, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to…
-
Hello Alexandre, There is a known bug about Control Chart for what you mentioned. The Atlassian issue below is for Jira Server but Jira Cloud probably has the same problem. https://jira.atlassian.com/browse/JSWSERVER-16449 If you are interested in a ready built alternative solution, our team at OBSS built Timepiece - Time…
-
Hello @Dorcas Chen , If you are interested in a ready built solution, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to…
-
By the way @Thomas Cucolo , updated > -6d means the update date is in the last 6 days, so that returns the issues that WERE updated in the last six days. If you want the issues that WERE NOT updated in the last six days, the JQL clause should be updated < -6d The same applies for the status change query that @Bill…
-
Hello @Darren Bryant , If you are interested in a ready built solution, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to…
-
Hello @d_sukhinina , Issue's histories already contain the raw data to calculate this information. You can see it as a Control Chart but Jira does not give the calculated data underneath. It just doesn't. The get this data from Jira Cloud, you have 3 options. * Use custom fields and workflow configurations to measure…
-
Hello @semer Mahmoud , The out of the box solution included in Jira Software for Cycle Time, Lead Time and similar metrics would be the Control Chart among Kanban Board Reports. It has limited customization options but might do the trick. For throughput you can run JQL queries like... project = ABC and status CHANGED FROM…