Comments
-
Hello @Teri Simonds , If you are OK with using a marketplace app for that, our team at OBSS built Timepiece - Time in Status for Jirafor these exact needs. 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 and on each assignee. Time in…
-
Hello @azanotti For getting linked issues from another project, I suggest you use an app. My favorite is Search Linked Issues (I am not related to this app). This app introduces new JQL functions that return issues that are linked to one of the issues in your JQL. Works just like the built-in JQL function " issue in…
-
Hello @Rita Sung , Our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud, and Data Center. Fundamentally, Time in Status allows you to see how much time each issue spent on each status and each assignee. The app also has 4 types of date reports. An issue can visit the same…
-
Hello @Larissa Akemi , Our team at OBSS built Timepiece - Time in Status for Jira for this. 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 and each assignee. You can define filters based on those times to see issues that spent more…
-
Hello @[deleted] Our team at OBSS built Timepiece - Time in Status for Jira for this. 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 and each assignee. You can combine status times into Consolidated Columns to get metrics like Cycle…
-
Hello @Ilaria , Our team at OBSS built Timepiece - Time in Status for Jira for this. 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 and each assignee. The app has custom calendar support so you can get the durations based on a standard…
-
Hello @Scott Kredo If you also have Jira Software, Control Chart of the Kanban boards might help a little about this. But I should note that the Control Chart in Jira offers very limited flexibility in terms of report parameters. For much greater flexibility and detailed reporting options, our team at OBSS built Time in…
-
Hello @Kyle Williams , The default Control Chart offers very limited flexibility in terms of report parameters. For much greater flexibility and detailed reporting options, our team at OBSS built Time in Status app for this. It is available for Jira Server, Cloud, and Data Center. Time in Status allows you to see how much…
-
Hello @Paras Sachan, For your fifth requirement and for similar needs about tracking times, our team at OBSS built Timepiece - Time in Status for Jira. 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 and each assignee. For all numeric…
-
Hello @Lisa Zanini , The data needed for this report is available in each issue's history but Jira does not provide this functionality out-of-the-box. If you are happy with serious custom development, you can try getting this data via REST API (changelog endpoint) and do the calculations yourself. If you are OK with using…
-
Hello @Rado I have got very good news for you. (I know this is an old post we answered before and I've already informed you through your support request but let me leave the news here for those following this post.) With this week's update, we released Multi Visit Behavior selection for Status Duration reports. Up until…
-
Hello @Vadym Kalujny Jira already tracks the history of status changes in each issue's history. You can see this data in the History tab of each issue. I don't recommend tracking this with a custom timer because users tend to forget to click on those buttons. Using the status history gives much better results. If you are…
-
Hello @Karen O_Regan The recommended approach here would be to move the issue to another status when you respond to the customer. In you use this case, our team at OBSS built Timepiece - Time in Status for Jira for this exact need and more. It is available for Jira Server, Cloud, and Data Center. Time in Status allows you…
-
Hello @Omar Khazamov Our team at OBSS built Timepiece - Time in Status for Jira for this exact need and more. 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 and each assignee. You can combine statuses into Consolidated Columns to see…
-
Hello @Christopher Marsh The data needed for this report is available in each issue's history but Jira does not provide this functionality out-of-the-box. If you are happy with serious custom development, you can try getting this data via REST API (changelog endpoint) and do the calculations yourself. If you are OK with…
-
Hello @Aleksandar Colic Our team at OBSS built Time in Status app for this exact need and more. 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 and each assignee. You can combine statuses into Consolidated Columns to see the total of…
-
Hello @Jason Liu, Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. It is available for Jira Server, Cloud, and Data Center. Using Time in Status, you can get ready analysis reports from the UI or REST API. First, your question: Time in Status can give you status transition dates…
-
Hello, Our team at OBSS built Timepiece - Time in Status for Jira for this exact need and more. 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 and each assignee. It also has Duration Between Statuses report that shows the duration…
-
Hello @Luke Our team at OBSS built Timepiece - Time in Status for Jira for this exact need and more. 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 and each assignee. You can calculate averages and sums of those durations grouped by…
-
Hello @Anantharaj I am not sure I understand your need perfectly but I believe you are trying to get a "Two Dimentional Filter Statistics" gadget, with one dimension being Status. The thing is, you want to display not each individual status, but you want to put them in status groups. If that is the case, I am sorry but it…
-
Hello @SHEHZADALI ISMAILY JQL gives you the option to filter by comparing specific dates on issues to current (or a given) date but you can't compare dates on issues with each other. That means (using JQL) you can ask to get issues that were updated less than 7 days before today but you can't get issues that were updated…
-
Yet the question stands... what are your requirements? What do you need to see in the report?
-
Hello @praktikant3 , Are your users actually logging work on tickets? Or are you looking for a solution that gets its data from how much time tickets spent in a status (for ex, "In Progress")? If your people are not logging time on tickets and you want to get data from status times, our team at OBSS built Timepiece - Time…
-
Hello @ori gal , I guess you want to use the velocity chart to get some kind of analysis about the trend of time spent on individual (or a group of) statuses in your workflow. Using the built-in Control Chart of Kanban boards might help with that since it allows you to inspect individual (not statuses but) board columns.…
-
Hello @Daria Pavlova , Jira does not give this information out of the box. If you are OK with using a marketplace app, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. It is available for Jira Server, Cloud, and Data Center. Time in Status allows you to see how much time each…
-
Hello @[deleted] , Control Chart is not very transparent about its inner workings and has very limited flexibility. If you are OK with using a marketplace app for this purpose, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. It is available for Jira Server, Cloud, and Data…
-
Hello @Ilya Konovalov , Jira does not give this information out of the box. The "Time spent" fields are about work logged onto issues by users, not time spent in statuses. Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. It is available for Jira Server, Cloud, and Data Center.…
-
Hello @kavita.desai Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. 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 and each assignee. You can calculate averages and sums of those durations…
-
Hello @Christoph Winkler Our team at OBSS built Time in Status app for this exact need and more. 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 and each assignee. You can calculate averages and sums of those durations grouped by the…
-
Hello @Pascal , Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need and more. 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 and each assignee. You can calculate averages and sums of those durations…