Service Desk app showing ticket duration by assignees and / or statuses

Service Desk app showing ticket duration by assignees and / or statuses

Service Desk app showing ticket duration by assignees and / or statuses

Monitor issue duration in real time

View total time in the specified status

Reporting on issue history statistics

Gather real time statistics by assignees and statuses. Easily track how long the issue was in a certain status, time spent, and who was working on it.

Configurable report setups helps you manage which data you are interested in monitoring to optimize your issue history reporting.

Use special project reports to monitor statistics by status or user, and time spent on each ticket. Perfect for SLA management.

Monitor issue duration in real time

View total time in the specified status

Reporting on issue history statistics

Leverage tabs with real time statistics by assignees and / or statuses and easily track how long the issue was in a certain status and who was working on it.

Calculated custom field shows how long an issue has been in a particular status. You can also opt to highlight the time if it exceeds a specified threshold (SLA management).

Use special project reports to monitor statistics by users and time spent on tickets.

More details

Issue History Collector for Jira cloud helps Project Managers and Stakeholders track issues easily and monitor how much time team members are spending on a request. You can monitor time QA logged on testing, Development – on building out a new feature, and Support – on closing out a client request so you can improve productivity.

Key features

View issue stats for the specified statuses and users, monitor ticket age in real time

Configurable reports to filter your ticket data

A dedicated report to see issue progress grouped by statuses tailored to your needs

Comprehensive view by assignees to monitor who and how long was working on the ticket

Main use cases

Track the amount of time that the ticket was in each of the statuses

Monitor time spent on the ticket by each assignee

Report on the ticket progress to identify roadblocks

We will be adding more features in the near future. If you need any assistance or would like to request a feature - we are just one click away!

Privacy and security

Privacy policy

Security

This vendor has completed the security self-assessment and shared the results with Atlassian.

Cloud app vendors are encouraged to complete a yearly self-assessment of their data security practices. This information is self-reported by vendors, and Atlassian is not responsible for the security or integrity of this app.

Very useful plug-in! Is there an ETA for making the time format configurable? When generating the Issue History report, I'd like to show all times in seconds so that we can aggregate the data more easily. The current nnd nnm nns makes that very difficult. Thanks!

No ETA yet but we do have it high up in our backlog. Thank you for your kind review, and should you have more ideas / feedback on the plugin, please do not hesitate to let us know - we're just one click away!

Very good plugin! Helps me with Kanban to produce statistics for Cycle and Lead Time! One request please! In the GROUP BY is it possible to add Issue Type? It's very critical to distinguish the statistics between types of jira tickets!

I was so pleased to find this plugin, until I found out that the plugin calculates Total Time as the current time, even after the user has Closed a ticket. This makes absolutely no sense. How can anyone get a correct delta of time between Open and Closed states, if the plugin keeps calculating Total Time even after the ticket has been closed for 30 days? That makes no sense at all.
A Closed status should not show the current time since the issue is done and is in a finite state,

Data Center Pricing

Pricing FAQ

Cloud apps are sold as a monthly or annual subscription. You are eligible for support and automatic version updates as long as your subscription is active.

When your subscription renews each month, you are automatically billed for apps based on the number of users in your instance.

If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

How do I determine my cloud pricing?

Apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you pay the 50-user price for apps.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for licensing across maximum users still apply.

The pricing structure for cloud apps is as follows:

Monthly subscriptions with up to 10 Atlassian product users are billed at a flat rate price.

Monthly subscriptions with more than 10 users are billed per user, starting at the first user.

Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.

If you've opted for annual billing for your Atlassian product, apps are also billed annually at a discount (12 months for the price of 10).

Do you offer academic, community, or open-source licenses for cloud apps?

Academic, community and open source licenses are not available for cloud apps.

Can I extend my free trial?

For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.

Cprime provides support for this app.

Cprime is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.