Emre Toptancı [OBSS] Atlassian Partner

Hello @Brandon Fay As you said, you can use the built-in Control Chart (that is available as part of Kanban Board reports) about this but it is not very good with reopens. It also will show you the duration but it does not show individual issues. It is more aimed towards seeing the big picture. You can also try the…

Hello @François DORION Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. IT can give you the statuses, dates and status durations. 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 @uday, You can do this with custom fields and automation rules (or workflow functions) but this solution will become harder and harder to maintain as the number of fields and statuses grows. And also, the dates you are looking for are already available in each issue's history. It is just hard to get them as a report.…

Hello @uday , You can do this with custom fields and automation rules (or workflow functions) but this solution will become harder and harder to maintain as the number of fields and statuses grows. And also, the dates you are looking for are already available in each issue's history. It is just hard to get them as a…

Hello @Faizan Iftikhar You can use the built-in Control Chart (that is available as part of Kanban Board reports) about this. It will show you the duration but it does not show individual issues. It is more aimed towards seeing the big picture. You can also try the built-in Average Age Report or Resolution Time Report.…

@Hello @Gomolemo Matsunyane Usuallyi when an issue is resolved, it transitions to a status named Resolved or Done. If you expect the report to work "irrespective of the status", how do you mark an issue as resolved? Do you set a value for the resolution field, without changing the status? EmreT

Hello @Angel Osberg For a ready-built solution that offers great flexibility and details, 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. You…

Hello @Diana Cabrejo This is not something Jira provides out of the box. You can set up something manually using automation rules and/or custom fields but that needs to be repeated for each status. This will be hard to maintain. The Jira Resolution Time reports or gadgets seem to provide this data but please note that they…

Hello @Maria Polischuk , Apparently what you mean by "Projects" is actually issues in projects, that is fine. "Cumulative Flow Diagram" (that is available as part of Kanban Boards) might help you. Also exporting your issue list to Excel (including the Resolution Date for each issue) and preparing a pivot report based on…

Hello @lucas.mara, This is not something Jira provides out of the box. You can set up something manually using automation rules and/or custom fields but that needs to be repeated for each status. This will be a nightmare to maintain. For a ready-built solution that offers great flexibility and details, our team at OBSS…

Hello @Prakhar Raj, If there is a discrepancy between what you see on the screen and what is recorded in the database, the difference might be related to timezones. Please check that your users (both Jira user profiles and user computer's settings) are set to the correct time zone. Based on the timezone of your users and…

@jnijjar , As the builders of Timepiece - Time in Status for Jira app mentioned above, I would like to make some contributions. There are multiple ways Timepiece can help you. You can use the Status Duration report of the app, which will effectively give you the time each issue spent on each status. Alternatively, you can…

Hello @[deleted] , First of all, most Jira reports that deal with issue resolution does not care about Resolved or Closed statuses. It all comes down to Resolution system field. For Jira, an unresolved issue is one that does not have a value for Resolution field. It is usually displayed as "Unresolved" on issues. A…

Hello @Pierre Kirry , What do you mean by "time spent"? Are you trying to report on the time (worklogs) actually logged on to issues by users? Or are you trying to see how much time issues spent on each status, assignee, etc.? EmreT

Updated the artice. @Jaime Capitel , hope it is better now. 

Hello @MARY USEN , Our team at OBSS recently released "Keychain - Delegation for Jira" app that provides the most comprehensive solution for delegating permissions. The app can delegate both Jira workflow permissions and JSM customer portal approvals. I suggest you have look. https://marketplace.atlassian.com/1225037 EmreT…

Hello @Arjen Uittenbogaard , The Resolution Time Chart shows the average resolution time of issues in your filter that were resolved on any given day. In other words, each bar represents the average resolution time of only the issues resolved on that day. If no issues were resolved on a given day, then no bar. The Average…

Hello Jonas, Our app primarily reports on individual issues. Reporting on linked issues is a little bit tricky. From a process perspective, I wouldn't recommend tracking this through multiple issues but that is a different story. Based on your current case you can try this approach if possible: Create a text custom field…

I would recommend building small teams (less than 10 people) and focusing on team productivity rather than individual output. An individual developer producing no apparent output might be supporting others in such a way that s/he might be contributing to the overall output more than anybody else. There is no healthy way to…

You see, this is more of a process question than a Jira one. Whichever path you take, Jira probably can provide a way to manage it. If any Backlog Item can go to any of the teams, then I would say you it sounds more like a single team (with subgroups) than 3 separate teams. In that case, 1 board, 1 sprint, and 1 burndown…

Hello @David Villacampa , This feels like a conflicting definition. Can you give more details? Does a single backlog mean that every item in the backlog can go to someone in any of the teams? Or do teams work with specified subsets of the backlog?

Hello @Fabian Lim , For an automated solution that offers great flexibility and details, 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 has many report types: * Status Duration and Assignee Duration reports allow you to see how much…

Hello Noel, Our team at OBSS built Time in Status app for this exact need. Along with many other reports, Time in Status has reports that show Status Counts or Transition Counts in each issue's history. You can calculate averages and sums of those counts grouped by issue fields you select. (For example, average reopen…

I am having the same issue while trying to upload a jar file from Manage Apps page on Jira DC. Using Chrome. I have Grammarly installed but turns out the problem was related to Dark Reader app. Didn't have to disable it. Turning it off for the site solved the issue.

Hello @Matthew O_Brien , There is no rule (in out-of-the-box Jira that enforces your users to enter worklogs only for the given day or week. Work can be logged on issues at any time for any date. This makes the report you want very problematic. Because users can log work for the sprint, even when the current date is…

Hello @Rob , For an automated solution that offers great flexibility and details, 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. You can also combine…

Hello @Sarah Chapman , Epics can be used as something like a work package that can span over multiple sprints. Putting planned start or end dates on Epics might make sense but I would say you shouldn't put time estimation and worklogs on them. In most cases, even "planned end date"s do not make sense due to the dynamic…

Hello @Kerina Naicker , For an automated solution that offers great flexibility and details, 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. You can…

Hello @Katryn Padrón , For an automated solution that offers great flexibility and details, 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. You…

Hello @Paul Isaacs , For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. It provides more fexible and detailed reports compared to Control Charts and it won't be affected by such bulk updates. It is available for Jira Server, Cloud and Data Center. Time in Status…