Emre Toptancı [OBSS] Atlassian Partner

Hello @Michael Walker , Control Chart works by showing the overall duration for a subset of columns and if your issue was reopened during its lifetime, Control Chart will show the total duration. Here is a quote from Control Chart documentation that points to this: Cycle time is the time spent working on an issue —…

Hello @Steven Groves If you are interested in a ready built solution, 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 each assignee or group. You can combine…

Hello @Chimena Ijeh , 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 @Andrew Thompson , 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 @Sai kumar 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 @Lilit Harutyunyan Jira keeps status transitions in its issue history but does not provide this information (or status durations) as a report. If you are interested in a ready built solution, our team at OBSS built Time in Status app exactly for this need. It is available for Jira Server, Cloud and Data Center. Among…

Hello @Puneet_Malik , Jira keeps status transitions in its issue history but does not provide this information (or status durations) as a report. You have a few options but before getting to those, I need to point two things here: First, an issue might visit the same status more than once so those dates will be different.…

Hello @Yana Nikolayeva , If you are interested in a ready built solution, 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 each assignee or group. The app shows…

Hello @Catarina Leite , Jira does not provide this report out-of-the-box but our team at OBSS created Time in Status app and Any Field Report in particular for this exact need. Time in Status has many report types, mostly to see the time each issue spent on each status, assignee, group, etc. On top of those, the newly…

Hello @Andreas Geißinger , The Cumulative Flow Diagram and especially Control Chart that are available in Kanban Board Reports might give better insight. Control Chart especially (with some limited configuration) can show times for a group of statuses. The downside is, it does not show individual issues and it is not…

Hello @Vaibhav Agarwal , As far as I understand, you want to see a list of issues with workflow status names as columns and the dates of entry to those statuses as values. I am afraid Jira does not provide this information out-of-the-box. You have a few options but first, two things to note here: First, an issue might…

Hello @Evelyn Dieppa , If you are interested in a ready built solution, 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 each assignee as well as entry/exit…

Hello @Harry Bob Jira Cloud does not provide a solution for this out of the box but 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 each assignee (and much…

Hello @amiram.fuerst , I am working as App Dev Team Lead at OBSS. We are the makers of Baselines for Confluence app. Let me leave a note here for you and for those who come by this thread in the future. We have plans to build a cloud version. The timeline is not set yet but I can say that it largely depends on customer…

Hello @Piotr Bojko , The features I see critical are: * Jira Server support (of course) * Creating a room and inviting participants with a single click from a Jira issue* (Hipchat had this. I am not sure if this is part of your bot scope but improves the usability significantly. Can be implemented as a companion Jira app.…

Hello @Chandra Pandey , As mentioned in other answers, you can use Jira REST API to get history data on each issue so you can filter out status changes. You did not indicate whether you are using server or cloud but if you are using Jira Server (or Data Center) and have access to the database, you can get the same data…

Hello @Lucia Sedlakova , Jira does not provide way to report on Lead Time or Cycle Time, out of the box. As you pointed out, Control Chart, that is available as a report in Kanban Boards of Jira Software, might be of use. While using a Kanban Board, you map your workflow statuses to board columns and to use the Control…

Hello @Frank Reveles , Our team at OBSS built Time in Status app for this 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 each assignee (and much more). You can combine statuses into consolidated columns to see…

Hello Stacy, Resolution Time gadget shows the average time of resolution. I believe most of your issues have similar resolution times but you probably have some issues on some specific days that have resolution times far above the average. When you group the gadget by days, those issues will increase the average of some…

Story, Task and Bug are (by default) standard issue types in Jira. That means they are not subtasks but parent tasks. The built-in Subtask issuetype is a sub-task issue type (please forgive the pun). It is just like any other issue (with its own key, summary, field values and workflow) but it is located as a subtask of…

Hello @Dionei Piazza , If an app is not an option, your best bet would be the Control Chart that is available as a report in Kanban Boards of Jira Software. While using the Control Chart, you can define a "quick filter" to filter only subtasks and define a board column to group workflow statuses that correspond to your…

Very very good news. Thank you very much. EmreT

Hello @d-vitaly Our team at OBSS built Time in Status app for this exact need. You didn't indicate your Jira platform but Time in Status by OBSS is available for Jira Server, Data Center and Cloud. Using Time in Status you can: * Report on how much time each issue spent on each status, on each assignee or on each user…

Hello @James Richards , One additional question related to this: Does this persistence cache hold the objects or the raw Bandana data? I mean, we keep objects in Bandana table but those objects are serialized so they can be kept as strings. BandanaManager deserializes the string and and gives us our object when we ask for…

Yesss, that is what I was looking for. Thanks a lot.

Thanks James, Just to be clear, it is not only about being able to flush Bandana Cache. It is also about seeing Bandana Cache details in Cache Statistics page. Thanks

Thank you James. The answer turned out to be different from what I expected but I believe you provided valuable information in this post that will benefit others. As a final note, since Bandana is one of the recommended ways of storing data for an app in Confluence, I think its caches should be listed in Cache Statistics…

Hello Vincent, Jira already keeps all issue history for each issue but that is not the same as Time Tracking. Time tracking refers to the actual work logged by users on that issue. By nature, this has to be made manually by users if you want to use the Original Estimation, Remaining Estimate or Time Spent fields on your…

Hi James, Thank you for the information. We presumed something similar to this cache behavior so we keep each item as a separate key/entry in the Bandana table. It might be several entries per space and thousands of entries in total on large systems (which is what we are testing for DC). Since it is what it is, can we say…

We have a marketplace app that is using the Bandana table for storing its data. We are currently working towards its official Confluence Data Center certification. Atlassian docs say that Confluence takes care of synchronizing Bandana caches between nodes but in a multinode DC environment the cache sync behavior is unknown…