Someone asks for a jsm customer satisfaction report. What they get is a shrug, a JQL export, or a screenshot of a few ticket scores. That is the reporting problem in one scene.
Symptoms
- No trusted trend line week-over-week
- Cannot answer “which request types drag CSAT down?”
- QBRs use anecdotes instead of satisfaction data
- Native views feel too thin; exports feel too heavy
- Low scores never show up as a managed workload
Why reporting breaks
Collection is incomplete. You cannot report what you barely receive — low response rates poison every chart.
Context is missing. A 2-star rating without queue, request type, assignee, and reopen history is a number, not an insight.
Ownership is unclear. A dashboard without a follow-up path becomes wallpaper. Reporting only matters when someone acts on the red cells.
Tools fight the system of record. If CSAT lives outside Jira, every report is a reconciliation project.
What leaders actually need
| Question | Reporting need |
|---|---|
| Are we getting better? | CSAT over time |
| Where does it hurt? | Break down by request type / queue |
| Are we recovering? | Volume and age of low-score follow-ups |
| Is collection healthy? | Response rate by channel |
If those four are hard, you do not have a “chart color” problem — you have a feedback operations problem.
Next step
When the diagnosis is clear, move to the jira csat reporting use case for how teams structure collection + reporting inside JSM.