Emre Toptancı [OBSS] Atlassian Partner

Hello @Sabrina Kesler Jira has this data in each issue's history but won't give it away as a ready to use report. You'll need to use a marketplace app for this. If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data…

Hello @MahanthPrudhvi , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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 and on each assignee.…

Hello @satba87 , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center. The best part is, our app uses existing Jira issue histories for its reporting so it will also work for your past…

Hello @MJ Y97 , The report you mentioned is an interesting one. It requires grouping issue history data not based on a date value on the issue but based on dates of individual status transitions. I am not aware of an easy option to do this in Jira (either with an OOTB feature or a marketplace app) The closest thing would…

Hello @Hemant Garg , I strongly suggest you not try to automate this. The timesheet data MUST be entered manually. I've seen many many customers trying to automate this and all those attempts either failed to build an automation or the resulting data was not trustworthy so they didn't use it. When you try to automate this,…

Hello @Elif Alverson , I should say upfront that the most healthy way to get this data is by making users enter worklogs. If you don't want your users to enter worklogs manually, the next best thing is to try to do the same through issue workflow statuses. You'll need to use a marketplace app for that. Our team at OBSS…

Hello @Ryan Jones , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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 and on each assignee. The…

Hello @Magdalena Widera Putting the timestamp of a transition to a custom field should be relatively easy with automation but more is needed to calculate metrics like Lead Time, Cycle Time, etc. Using a marketplace app will provide much more analysis capabilities for you. I can recommend Timepiece - Time in Status for…

Hello @Achraf MECHTA , This is a hard one. I don't know of any out-of-the-box features or apps that will give you a report in this format. I see that you are trying to see what piece of work each developer worked on and how long it took for the developer to finish it. But I must say, this format can be really misleading. I…

Hello @Yana Neverko , Some of the things you ask can be achieved with simple JQL. (I presume you change the status and/or assignees of tickets while escalating between different teams) You can use the template JQL below to filter issues based on their status and assignee changes assignee was admin //assignee is currently…

Hello @Achraf MECHTA , Can you give a little more detail about your need? A sample output you expect would be very useful the understand the format you need. Thanks.

Hello, If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. I can recommend our app for your need number 2 and 4. It is available for Jira Server, Cloud, and Data Center. (I presumed service recovery times are also measured through issue…

Hello @Manuel.MAULINE , Sorry we can't respond in French but I hope my below answer in English can help you. Jira's own Control Chart, Age and Created vs Resolved charts offer limited detail and flexibility. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for…

Hello @Søren Hansen , I am from OBSS and we are one of the vendors that built such an app, Timepiece - Time in Status for Jira. Your options are limited without using an app (That is why we built the app in the first place). If you have Jira Software, you can use the Control Chart that is part of Kanban Boards. The Control…

Hello @Anthony Martinez , Presuming that all stages of the lifecycle of an incident and/or service are represented by workflow statuses on your system, I can recommend our app Timepiece - Time in Status for Jira that let's you create reports based on these status changes. It is available for Jira Server, Cloud, and Data…

Hello @Integrador (Admin) , Jira's own Age and Created vs Resolved charts offer limited detail and flexibility. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly…

Hello @Anthony Martin I am glad to hear that you are using and benefiting from Time in Status by OBSS. You know, the procurement of a marketplace app by Atlassian very very rarely happens and under special circumstances. I can't comment on its future possibility. All I can say is that such an idea never came up so far.…

Hello @Niranjan Deshpande and @Eman Mostafa , This is an old post but since you are still following it, please let me respond by explaining how you can get Cycle Time and Lead Time in two different ways with our app Time in Status by OBSS. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly…

Hello @Jamie Edmondson , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center. You can get this data (and more) on your issues with Time in Status. Time in Status does not add a custom…

Hello @Yaron Azar Currently, there is no integration between our app and Jira Automation, mainly because Atlassian doesn't have automation integration points for marketplace apps yet. We are eagerly waiting for that. There is a feature request made to Atlassian about this. I suggest you watch it and vote for it:…

Hello @Vivek Garg Can you provide a little more detail? Which Cycle Time are you asking about? Which screen? Which report? EmreT

Hello @Rajeev Desai If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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 and on each assignee. Time…

Hello @Joshua Chu If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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 and on each assignee. Time in…

Hello @khushboo_puri, Since the value you see on the screen says 2 days 23 hours, we can safely assume that 1 day equals 24 hours. Control Chart provides little insight into its inner workings and offers limited flexibility regarding report parameters. Our team at OBSS built Timepiece - Time in Status for Jira for this…

Hello @mark 1 , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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 and on each assignee. Time in…

Hello @Harrica Rion If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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 and on each assignee. Time…

Hello @mahmoud burhamy , I am sorry but you can't get this data with a simple JQL query. Jira does not offer this out-of-the-box, but the data needed for this report is available in each issue's history. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this…

Hello @Anu Issac You can click on the issuetype icon and select a new type. This will only work if Story and Task types are using the same workflow. If they are not using the same workflow, you can use the "Move" option in the context menu and move your issues to the same project with a new issuetype. EmreT

Hello @Andrii (PM) , When it comes to time tracking, there are two general approaches. I should note upfront that these approaches serve different purposes and are NOT alternatives to each other. You may choose to employ either one or both. Work Logs The first one is work logging. You tell your users to manually log the…

Hello @Alba Charles Jira does not offer this out-of-the-box, but the data needed for this report is available in each issue's history. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center.…