Burnout Radar for Jira – User Guide

Overview

Burnout Radar counts signals of overload in your own Jira work — logged hours, overdue and unresolved issues, blockers, high-priority work, SLA pressure — and shows which of them passed their limit in a week or a month.

Two things matter most:

• Your reports are private. You see them; nobody else does unless you share them. Being a Jira or project admin does not let anyone see them.
• It is not a medical tool. It counts work signals; it does not measure health and a raised signal is not a diagnosis.

The app runs on Atlassian Forge, stores its reports in your Atlassian site and makes no external calls.

---

Open your work signals

1. Install Burnout Radar from the Atlassian Marketplace (a Jira admin approves the permissions).
2. In Jira’s sidebar, open Apps → My Burnout Radar. Every user of the site can open it.

The page, My work signals, has four tabs: My reports, Create a report, Shared with me and My data. The ? button explains the open tab. On your first visit a short note shows the three steps — create a report, see your signals, share only if you want — until you press Got it.

---

Create a report

On Create a report, choose Weekly or Monthly, the Year, the Month and, for a weekly report, the Week (ISO weeks, Monday to Sunday). Create report reads your Jira work for that period and saves the report.

• A period that has not ended yet asks first (Create anyway / Cancel); future periods cannot be created.
• If the period already has a report, the app asks before replacing it.
• No issue in the period: “No issues were found for the specified period.”

What is counted. The issues you were assigned to, now or at some point, that were updated or had work logged in the period: the time you logged on days inside the period, due dates, priorities, statuses, resolutions, subtasks, “is blocked by” links and — on Jira Service Management sites — SLA fields. The app keeps counts and times only; it does not store issue titles, descriptions, comments or worklog texts.

---

My reports

• Period, Year and Month choose which reports are listed.
• How many signals did each week raise? — one bar per week (or month): the signals raised out of the 11 a report can raise. A gap is a period without a report; select a bar to open that report.
• The table lists each report with a short Summary (overdue issues, issues with logged time), the Signals raised (“5/11”) and View Details / Delete.

Read a report

View Details opens what matters first — every signal with this period’s figure, the limit it was compared with and whether it was raised:

ⓘ beside a signal’s name says the same in the app, with the limit it was raised at. Below the table, Which signals passed their limit? draws each figure as a share of its own limit — past the line, the signal is raised:

Which days were busiest? shows the hours logged and the issues completed on each day, with the busiest day named in words:

More details opens the rest — workload, deadlines, priorities, what waits on what, subtasks, where your issues are now, hours in the current status, resolutions and SLA — each chart titled with the question it answers and the limit of the signal that watches it. Fewer details closes them again. A report keeps the limits it was created with, so an old report reads the same later.

How did the week feel?

At the top of My reports the app asks How did week 43 feel? — Very hard, Hard, Okay, Good or Very good — with an optional note for yourself. Not now waits until next week.

Only you can see it — not the people you share reports with, not Team overview, not the Rovo agent. On your own weekly chart a week that felt hard or very hard gets a mark. Saved answers can be changed or deleted.

---

Share your reports — only if you want

Open My data → Who can see your reports, pick a person and press Share my reports. They see your reports under their Shared with me and can create them for you, until you choose Stop sharing with ….

Shared with me shows the reports of the people who shared theirs with you: one column per person, one row per week, each person’s signals (“2/11”) and a chart How many signals did each person’s week raise?. Your Jira role adds no one.

---

My data — see and delete what is kept

My data lists what the app keeps about you: your reports by year, your check-ins, saved views, the view rights that name you, and your entry in the app’s register.

• Download my data (JSON) saves a copy, made in your browser.
• Delete everything about me… asks first, then deletes all of it. Your work in Jira does not change.

When an Atlassian account is closed, the app learns it from Atlassian and deletes that person’s reports and everything else it keeps about them.

---

Team overview (admins)

Jira admins open Jira settings → Apps → Burnout Radar; project admins find Burnout Radar in their project’s navigation. The page, Team overview, has three tabs: Team overview, Thresholds and What is kept.

Team overview shows a group’s or a project’s totals only — never a person’s own report or name:

• Choose a Group or a Project (on a project page it is that project), the report type, year and month.
• How many people raised each signal? — for each signal, the share of the people with a report who raised it.
• The table says the same in words: People with a report (“6 of 6”), each signal (“1 of 6”) and the average signals per person.
• A week or month is shown only when at least 5 people have a report for it; otherwise its cells say “—”, so no single person’s numbers show.

Thresholds and what is kept

Thresholds sets the limit of every signal, separately for weekly and monthly reports, with a line on what each one means:

Save Thresholds applies them to every report created afterwards, for everyone. What is kept chooses which categories of figures (SLA, workload, deadlines, workflow, priority, complexity, dependency, resolution, trends) and which signals reports keep.

---

The Rovo agent

On sites with Rovo, open Rovo chat and choose Burnout Radar by Simplify, or start with “Analyze my Burnout Radar reports and trends”. The agent reads your own stored reports — the current and previous month and the last four weeks — and answers with a summary, practical suggestions and supportive words. It never receives other people’s data, issue texts or names, and it does not create reports: create them on My work signals first. It is not medical advice; if you feel overwhelmed or unsafe, contact a professional or your local emergency number.

---

Permissions and data

• Scopes: read:jira-work (issues, worklogs, fields), read:jira-user (people and groups), manage:jira-configuration (Atlassian’s scope for listing a group’s members), storage:app (reports and settings) and report:personal-data (learn about closed accounts to delete their data).
• Where data lives: in the app’s Forge storage inside your Atlassian site. No data leaves Atlassian; the agent runs in Atlassian’s Rovo.
• Who sees what: a person’s reports — that person and the people they shared with; Team overview — groups and projects of at least 5 people with a report, totals only; check-ins — the person only.

See the privacy policy and the data processing addendum.

---

Troubleshooting

• “No issues were found for the specified period.” — you had no assigned issues updated or worked on then.
• A signal looks too high or too low — the limits are the site’s; a Jira admin changes them under Thresholds. Reports keep the limits they were created with: create the report again to use the new ones.
• Team overview shows “—” — fewer than 5 people have a report for that period.
• “Burnout Radar needs an active licence.” — a Jira admin renews it in Manage apps.

Still stuck? Contact support.

---

Related apps

• Workload & Capacity Planner — the team’s hours against weekly capacity, rebalanced by drag and drop.
• OutSync — leave and out of office on your Jira board, synced with Google Calendar.
• Report Assistant — daily and weekly status reports written from your Jira activity.