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.]
| Info |
|---|
To view reports of an on-call team, you must be a team admin. Learn more about roles, permissions, and rights |
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 | ||
|---|---|---|
| ||
|
...
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
| Panel | ||
|---|---|---|
| ||
There are some team reports that aren't available at a site level.
There are also some site reports that aren’t available at a team level.
|
| Expand | ||
|---|---|---|
| ||
|
| Expand | ||
|---|---|---|
| ||
|
...
| Info |
|---|
Share your feedbackWe would love to receive feedback about this documentation, the product experience, functionality, or anything you’ve got to share. You can either add comments to this page or add a card on the Trello board. |
...
| Expand | ||
|---|---|---|
| ||
Reports of your on-call team A team report focuses on your on-call team’s activities, performance, and the alerts that your team members receive. The different categories of team reports are—productivity, alerts, incidents, on-call, API, and DevOps.
|
| Expand | ||
|---|---|---|
| ||
Do not go beyond this point ⚠️
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:
(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: (not types of report but the way they’re accessed) Name options for Team Reports:
Name options for site 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 |
...