Jira Key metrics for activity: custom Jira Scripts with Report Builder | part 5 - Actonic – Unfolding your potential
We have outsourced our Atlassian licensing and services business to the newly founded Seibert Solutions GmbH. Actonic's products will be further developed under the usual name.

Jira Key metrics for activity: custom Jira Scripts with Report Builder | part 5


5
(1)

When working in a Service Management support team, you as a member or a team lead will need to know about the most important key metrics. This entails monitoring activities like comments as well as comparing created vs. resolved tickets.

Report Builder report "Key metrics for activity"

Comments

Monitoring comment content as well as their quantity can lead to problem discovery and might help with avoiding the same problems in the future. It’s also a hint for potential delays and effects on Service Level Agreements (SLAs), which could be relevant for your customers.

Created vs. resolved tickets

Comparing your numbers of created vs. resolved tickets is displaying your support team’s workload, their progress and could be a hint for resource needs.

"Key metrics for activity"

Our time tracking and reporting all Report Builder is extending default functions of ticket systems like Jira Service Management or Zendesk. One example is our report “Key metrics for activity”. It’s displaying metrics and changes for important KPIs in support teams.

The report gives you at-a-glance metrics for:

  • created and solved tickets
  • number of comments
  • active authors
  • and much more

For each report you can see the percentage of change compared to the previous 7 or 30 days.

Test Report Builder for free on our Atlassian Marketplace

Next level Jira Reporting with Report Builder

  • Create your own Jira custom reports
  • Use customizable templates
  • Export reports to CSV, Excel or PDF
Go to Atlassian Marketplace

How useful was this post?

Click on a star to rate it!

Average rating 5 / 5. Vote count: 1

No votes so far! Be the first to rate this post.