Burnout Radar: Private Workload & Stress Signals for Jira
Burnout Radar spots overload early from real Jira work. Each week it counts signals — logged hours, overdue issues, blockers, high-priority work, SLA pressure — and shows which passed their limit. The reports belong to the person: private by default, shared only by their choice.
- Try it free on the Atlassian Marketplace
- How much does a 60-hour week really produce? (free simulator)
- Read the documentation
Signals from real Jira work
Eleven signals from your own issues: logged time, overdue and due-soon issues, unresolved and blocked issues, high-priority work, long-running issues, SLAs close to breach and breached. Each report shows every figure next to the limit it was compared with, so a raised signal is never a mystery.
Private by design
You decide who sees your reports. Nobody does until you share them — admins can’t, managers can’t. My data shows everything the app keeps about you, downloads it, and deletes it on request.
Team totals, never names
Team leads and admins see how many people in a group or project raised each signal — only for weeks with at least 5 reports, so no one is singled out. Thresholds are set once for the whole site.
Also included
- A private weekly check-in — how the week felt, seen only by you.
- Which days were busiest — hours logged and issues completed per day.
- Weekly and monthly reports, a chart of signals per week, and every detail chart titled with the question it answers.
- Sharing by consent — one person at a time, until you stop.
- Rovo agent “Burnout Radar by Simplify” — a summary and practical suggestions from your own reports (on sites with Rovo).
- Site thresholds for every signal, weekly and monthly.
Not a medical tool
Burnout Radar counts signals of workload and deadline pressure in Jira. It does not measure anyone’s health, and its Rovo agent says so in every answer. If someone feels overwhelmed, the right next step is a conversation — or a professional.
Runs on Atlassian
Built on Atlassian Forge: reports are stored inside your Atlassian site, no data leaves Atlassian, and closed Atlassian accounts are erased automatically. See the privacy policy and the data processing addendum.
Related apps
- Workload & Capacity Planner — 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.
Planning around people who are away? Read the ghost resource problem.
Frequently asked questions
Can my manager or a Jira admin see my reports?
No. Your reports are seen only by you and by the people you choose to share them with. Being a Jira or project admin does not let anyone see them; admins see totals of groups or projects with at least 5 people, never names.
What does Burnout Radar count?
Eleven signals from your own Jira work in a week or month — logged hours, overdue, due-soon and unresolved issues, issues worked on, high-priority and blocked issues, issues with many subtasks, long-running issues, SLAs close to breach and SLA breaches — each against a limit your admin sets.
Is it a medical or mental-health tool?
No. It counts signals in Jira work; it cannot see how anyone feels, and a raised signal is not a diagnosis.
Can I delete what the app stores about me?
Yes. My data lists everything the app keeps about you, lets you download it as JSON and deletes all of it with one confirmation. Your Jira work does not change.
Does any data leave Atlassian?
No. The app reads Jira through Atlassian's API, stores reports in its Forge storage inside your site and makes no external calls. The optional Rovo agent runs in Atlassian's Rovo and reads only your own reports.