Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Reports give you analytics and data visualization capabilities on how you use operations in JSM, how things are changing over time, and how your teams are performing.

...

  • Productivity (Team productivity, Responder productivity)

  • Alerts (Alert MTTA/C, Alert analytics)

  • Incidents (Post-incident reviews, ICC sessions, Incident analytics)

  • On-call (On-call time analytics, Total on-call time per user)

  • API (API usage analytics, API usage analytics by time)

  • DevOps (DevOps metrics) [need to check - differences in names]

[productivity, alerts, incidents, on-call, API, and DevOps.]

...

At a given point, you can access the report of only one on-call team that you have team admin rights to.

E.g.: If you are the team admin of Team A and Team B, you cannot view reports of both teams simultaneously. If you’re viewing Team A’s report at a point, you can’t view Team B’s report. You’ve to navigate to Team B’s reports separately to view it. Learn how to view reports of an on-call team

Expand
titleTo add - by VS
  • Where to find team reports

  • What categories of reports exist (alerts, on-call, notifications) —

  • About the switcher that shows you site reports at a team level (only for site admins). (Q. Do we need to talk about this here? The idea of site admin hasn’t been introduced yet to the reader. Talking about site admin or site-level reports might confuse the reader IMO)

  • We can also clarify that you can view only this team’s reports (if you’re just a team admin), so they gotta navigate to a different team’s Operations > Reports to see it’s reports — you can’t access team2’s reports it from team1 — maybe this is obvious?

...

These reports give you a general analysis of notifications, API usage, and other metrics that are common across several on-call teams on the entire site. These reports link to only those teams that use operations.

These are the The types of reports of for all on-call teams:

  • Alerts (Monthly overview, Alert MTTA/C, Team MTTA/C, Alert analytics)

  • Productivity (Responder productivity)

  • Incidents (Post-incident reviews, ICC sessions, Infrastructure health)

  • On-call (Total on-call time per user)

  • API (API usage analytics, API usage analytics by time, API rate limits)

  • DevOps (DevOps metrics)

  • Notifications (Notification analytics, Notification analytics by user, Incoming call routing)

  • Other (User management)

...

At a given point, you can access the report of either one on-call team or the reports of all on-call teams across the site. It isn't possible for you to selectively pick specific on-call teams and view the reports of only those.

You can view site-level reports in two ways:

i. From Teams view via Ops Dashboard

ii. From Jira site settings

Learn how to view reports of all on-call teams

Panel
bgColor#B3D4FF

There are some team reports that aren't available at a site level.

  • Productivity (Team productivity)

  • Incidents (Incident analytics)

  • On-call (On-call time analytics)

There are also some site reports that aren’t available at a team level.

  • Alerts (Monthly overview, Team MTTA/C)

  • Incidents (Infrastructure health)

  • API (API rate limits)

  • Notifications (Notification analytics, Notification analytics by user, Incoming call routing)

  • Other (User management)

...

Expand
titleRough work - V1

Do not go beyond this point ⚠️

Info

Structure

Heading or topic

Simplified explanation in my words

Explanation from documentation

– – –

Overview

(my words)

Reports give you a pictorial understanding (like charts and diagrams) of how you’re using JSM, how your teams are doing and how things are changing with time.

Reports are of two types depending on what they’re connected/mapped to:

  • Team reports

  • Project/Site/Global reports

(edited from the old documentation)

Reports give you analytics and data visualization capabilities on how you use JSM, how things are changing over time, and how your teams are performing. We create these reports by using a tool from a partner brand. This tool is called Looker.

There are two different types of reports in JSM:
a. Team reports
b. Project reports

(not types of report but the way they’re accessed)

Name options for Team Reports:

  • On-call team report

  • Report of your on-call team

  • Your on-call team report

Name options for site reports:

  • Site reports

  • Site-level on-call report

  • On-call reports of other teams

  • Multiple on-call team reports

  • Multiple team reports

  • All on-call team reports


a. Team reports

(my words)

These are the reports that are mapped to a certain team. It will give you information in the form of charts, bar graphs, etc. about your team’s performance, their activities, and the alerts they get.

These are alerts and on-call reports.

[Q. Do we need to mention that if you’re a team admin, not all team reports are visible to you?

Q. Or mention about different Admin rights because that seems to be closely connected to how one views certain reports? I feel this knowledge would give them some visibility.

(edited from the old documentation)

Team reports focus on your team activities, performance, and the alerts that your team members receive.

[These reports also include some common looks with the Global Reports which focus only on the particular team that is selected.]


b. (Project/Site) reports

(my words)

These reports will give you a many teams' information. This has info of several other on-call teams' data and performance metrics

...