Data and Privacy
What JiraMetrics.Pro requests from Jira, what is processed in your browser, and why the content of your tasks never enters the plugin at all.
The Core Principle
Flow metrics need just two things: the issue key and the moments it moved between columns. That's enough to calculate lead time, throughput, CFD, and everything else.
That's why JMP never requests task titles, descriptions, comments, or assignees. They don't enter the plugin for a single moment — which means the content of your tasks simply has nowhere to leak from: it isn't in JMP.
The transition history itself is loaded from your Jira straight into your browser, and every metric is calculated on your own computer.
What Gets Sent, and Where
| Destination | What's sent | When |
|---|---|---|
| Your Jira | Requests for board configuration and task transition history — using your own Jira session | When loading a board and its reports |
| JMP Cloud (account) | Sign-in profile and dashboard configuration: dashboard and widget names, chosen chart types, column/swimlane/filter IDs, date ranges | If you're signed in and use dashboards |
| Analytics (Google Analytics) | Anonymous interface usage events (for example, "report opened", "widget created") with a random installation identifier | In the background, while you use the app |
More detail on each destination:
- Jira. JMP talks only to your own Jira instance, and only for two things: the board configuration and the history of tasks moving between columns. It uses your current browser Jira session — JMP never requests or stores separate tokens or passwords.
- JMP Cloud. The cloud stores the configuration of your dashboards, so they're available from any computer and via sharing links. This is metadata: widget names and which filters are selected in them. The tasks themselves and their timings are never written to the cloud.
- Analytics. Events describe actions in the interface: which report was opened, which widget type was created, which filter was clicked. They contain no address of your Jira, no board name, and no task keys; the only Jira-related value that can appear is the numeric identifier of the quick filter you clicked. The installation identifier is random and isn't tied to your account or your Jira.
What This Means in Practice
When a company asks whether the extension is safe to install, the concern is usually the same: could the wording of tasks, the discussion in comments, and who is working on what get out? With JMP the answer is short — the plugin never receives that data. It sees that PROJ-123 moved from one column to another at a certain moment, and nothing more.
What's Stored on Your Computer
Locally (in browser storage) live: the Jira address and board number, the loaded board structure (column, swimlane, and quick filter names), selected filters and date range, the list of recent boards, favorite dashboards, theme, and interface settings. If you clear your browser data:
- settings and filters reset to their defaults;
- dashboards aren't lost — they're stored in the cloud and come back once you sign in;
- the transition history is loaded from Jira again the next time you open the app.
Last updated on
Task Flow
How to open and read the Task Flow dialog in JiraMetrics.Pro — a breakdown of a task's journey across board columns, finding the causes of long lead times, and preparing material for retrospectives.
FAQ and Troubleshooting
Answers to common questions about JiraMetrics.Pro - board loading errors, empty reports, missing dashboards, supported Jira versions.