ReportInSite Playbook

How to turn a Jira export, a CSV or numbers you type in into a scorecard, a sprint report and a cross-team roll-up you can send to a steering group. It takes about ten minutes the first time.

Open the tool →Open it with sample data

• 1 · Quick start
• 2 · Get your data in
• 3 · Data from any app
• 4 · Set your targets
• 5 · Read the scorecard
• 6 · Sprint report
• 7 · Cross-team roll-up
• 8 · Trends over time
• 9 · Export & share
• 10 · Your data & backups
• 11 · Troubleshooting

1 · Quick start

1. Open the tool at reportinsite.com.au/tools/reportinsite. You can start without an account. Type your organisation's name in the box at the top left; it goes on your PDFs.
2. Import your data. Open the Data tab, choose how your data arrives, and import it (see section 2). Sprint data, incidents, deployments, budgets and survey results can all come in; section 3 has a recipe for each app.
3. Set targets. On the Framework tab, give each metric you care about a target. Metrics without a target show grey.
4. Read the report. The Scorecard, Sprint report, Roll-up and Trends tabs fill in automatically.
5. Export. Export & share → PDF — steering pack gives you a landscape PDF of the whole picture.

2 · Get your data in

On the Data tab, under Add data, pick the option that matches what you have:

Sprint summary columns

Team, Sprint, Start, End, Committed SP, Delivered SP, Not Completed SP, Removed SP, Issues Completed, Lead Time

• Dates can be 2026-09-14, 14/09/2026 or Jira's 14/Sep/26.
• If you leave out Not Completed SP, it's worked out as committed minus delivered.
• If the file has no Team column, type the team name in the Team box before importing.
• Commas, semicolons and tab-separated files all work, and so do Excel files (.xlsx). Title rows above the column headers are skipped.

Importing again

Re-importing a sprint with the same team and name replaces it, so you can safely re-run an export each sprint. Teams and sprints are listed lower down the Data tab, where you can rename or remove them.

3 · Data from any app

Every metric on the framework can be fed from a file, not just the sprint ones. On the Data tab choose Any data: CSV or Excel, pick the recipe for your app, and follow its export steps. The recipe fills in the column mapping and the calculation for you; you can change any of it before importing. Each recipe also has Try it with sample data, so you can see the result before exporting anything.

How a file becomes a metric

1. Team. A column that says which team each row belongs to (assignment group, area path, project, cost centre), or one team for the whole file, or the organisation as a whole (Portfolio).
2. Month. A date column groups rows by month. The latest month goes on the scorecard; earlier months appear on Trends. Leave it out for "as of today" counts such as open backlog.
3. Calculation. count rows; count distinct values; sum of a column; average of a column; median of a column; 85th percentile of a column; lowest value; highest value; % of rows matching a condition; % of a column's total where a condition holds; column a ÷ column b, as %; column a − column b (totals); average of column a × column b; time between two dates; age: today − a date; net promoter score (0–10 answers); rows per week.
4. Filters. Keep only the rows you want, e.g. Priority is one of 1, 2, or Status is not Closed.
5. Metric. Choose where the number goes. Recipes for DORA, Flow and Service Management metrics add those areas to your framework if they aren't there yet.

Dev tools

project = ABC AND issuetype = Bug AND created >= startOfMonth(-5) AND (labels = production OR environment ~ "prod") ORDER BY created DESC

project = ABC AND labels = tech-debt AND statusCategory != Done ORDER BY priority DESC

project = ABC AND statusCategory = Done AND resolved >= startOfMonth(-5) AND issuetype in (Story, Task, Bug) ORDER BY resolved DESC

SELECT [System.Id], [System.WorkItemType], [System.Title], [System.State], [System.IterationPath], [System.AreaPath], [Microsoft.VSTS.Scheduling.StoryPoints], [System.CreatedDate], [Microsoft.VSTS.Common.ClosedDate]
FROM WorkItems
WHERE [System.TeamProject] = @project
  AND [System.WorkItemType] IN ('User Story', 'Bug', 'Task')
  AND [System.IterationPath] UNDER @project
  AND [System.ChangedDate] >= @today - 180
ORDER BY [System.IterationPath]

SELECT [System.Id], [System.WorkItemType], [System.AreaPath], [Microsoft.VSTS.Common.ActivatedDate], [Microsoft.VSTS.Common.ClosedDate]
FROM WorkItems
WHERE [System.TeamProject] = @project
  AND [System.State] = 'Closed'
  AND [Microsoft.VSTS.Common.ClosedDate] >= @today - 180

Test runs completed in the last 6 months; include Outcome (or Status), Run date and Team / Suite.

gh run list --workflow deploy.yml --branch main --limit 1000 \
  --json createdAt,conclusion,headBranch \
  --jq '["created","conclusion","branch"], (.[] | [.createdAt, .conclusion, .headBranch]) | @csv' > deploys.csv

gh pr list --state merged --base main --limit 1000 \
  --json number,createdAt,mergedAt \
  --jq '["number","created","merged"], (.[] | [.number, .createdAt, .mergedAt]) | @csv' > prs.csv

gh issue list --state closed --limit 2000 \
  --json number,title,labels,createdAt,closedAt \
  --jq '["number","title","labels","created","closed"], (.[] | [.number, .title, ([.labels[].name] | join(";")), .createdAt, .closedAt]) | @csv' > issues.csv

glab api "projects/123/deployments?environment=production&status=success&per_page=100" --paginate \
  | jq -r '["created","status","ref"], (.[] | [.created_at, .status, .ref]) | @csv' > deploys.csv

(printf "finished\tresult\tbranch\n"; az pipelines runs list --pipeline-ids 42 --top 1000 \
  --query "[].[finishTime, result, sourceBranch]" -o tsv) > deploys.tsv

Team is <your team> · Cycle is any of <last 6 cycles> · Type: all issues

Status type is Completed · Completed date is after 6 months ago

Work management

Filter: Sprint is any of <last 6 sprints>. Show columns: Name, Sprint, Status, Story Points, Team.

Filter: Status is Done · Completion date is in the last 6 months

Advanced search → Completed: within the last 6 months · In projects: <your projects> → Export CSV

Completed: within the last 6 months · In projects: <your projects>

Sprint folder · All lists · Include closed tasks · Columns: Task Name, Status, Sprint Points, List Name, Date Created, Date Closed

Filter: Status is closed · Date Closed is last 6 months

Cards in list "Done" (archive older cards to keep the export small)

project = ABC AND statusCategory = "In Progress" ORDER BY updated DESC

SELECT [System.Id], [System.AreaPath], [Microsoft.VSTS.Common.ActivatedDate] FROM WorkItems WHERE [System.TeamProject] = @project AND [System.State] = 'Active'

Service & ops

resolved_atRELATIVEGT@month@ago@6^ORDERBYDESCresolved_at

priorityIN1,2^resolved_atRELATIVEGT@month@ago@6

priorityIN1,2^resolved_atRELATIVEGT@month@ago@6

resolved_atRELATIVEGT@month@ago@6

opened_atRELATIVEGT@month@ago@6^ORDERBYopened_at

active=true^stateNOT IN6,7,8

resolved_atRELATIVEGT@month@ago@6

closed_atRELATIVEGT@month@ago@6^close_codeISNOTEMPTY

project = SUP AND resolved >= startOfMonth(-5) ORDER BY resolved DESC

project = SUP AND issuetype = "Service Request" AND resolved >= startOfMonth(-5) ORDER BY resolved DESC

Uptime report, daily granularity, last 6 months, all production monitors

SELECT count(*) AS 'Total', filter(count(*), WHERE httpResponseCode < 500) AS 'Successful' FROM Transaction FACET appName SINCE 6 months ago TIMESERIES 1 day

Business data

Budget variance by month, operating expenses, by tracking category / cost centre, last 6 months

Chargebacks by team and month: Planned recharge, Actual recharge

Detailed time report, last 6 months, grouped by person, with Billable flag

"How likely are you to recommend us to a friend or colleague?" (0–10), plus the response date and (optionally) a team / product question

"Overall, how satisfied are you?" (1–5)

Team (choice) · "Rate your team's practice maturity" (1–5) · response date

Columns: Team, Person, Skill, Level (1–5)

All risks with Status not Closed; columns Team / Owner area, Likelihood, Impact, Status

categoryLIKEprivacy^sys_created_onRELATIVEGT@month@ago@12

4 · Set your targets

The Framework tab holds the areas and metrics on your scorecard. The default has eight areas: Delivery, Operations, Systems Performance, Quality, DevOps & Culture, Financial, Strategic & Risk and Customer Satisfaction. For each metric you can set:

• Target: the number you're aiming for.
• Better when: Higher (velocity, NPS) or Lower (lead time, defects).
• Amber band: how far off target still counts as "near" (5%, 10%, 20% or 30%).
• Source: Entered means you type or import the value. Auto means it's calculated from sprint data (velocity, commitment ratio, completion rate, throughput, scope change, lead time).
• Roll-up: how team values combine into the portfolio figure: mean, sum or worst.

Rename, add or remove anything to fit how your organisation reports. If you want to start lean, pick Lean delivery from the template list and click Replace with template.

To add whole areas beside the ones you have, pick a pack and click Add to framework:

• DORA: Deployment Frequency, Lead Time for Changes, Change Failure Rate, Time to Restore Service.
• Flow: Cycle Time (85th percentile), Throughput, Work in Progress, Work Item Age, Flow Efficiency.
• Service management: Incident Volume, Mean Time to Resolve, SLA Met, Open Backlog, First Contact Resolution.

5 · Read the scorecard

The Scorecard shows every metric for one team, or for the whole portfolio, with a status against its target:

• On target: at or better than the target.
• Near target: worse than target, but within the amber band.
• Off target: beyond the amber band. A target of 0 (e.g. security breaches) has no amber band, so anything above it is red.
• No target: no target set, or no value yet.

Use the team buttons at the top right to switch between teams and Portfolio. Auto metrics fill themselves in from each team's latest sprint, and you can type entered metrics straight into the table. On the portfolio view, auto metrics pool every team's points (not an average of percentages), and entered metrics roll up from the teams unless you type a portfolio figure.

6 · Sprint report

The Sprint report tab covers one sprint for one team: committed vs delivered points, a scope waterfall, velocity across sprints, issue types and, if you pasted a Sprint Report, the issues themselves. There's space for sprint goals, an executive summary and recommendations, which are included in the PDF.

The three rates

When the rates differ, the gap is scope change. The report spells out how much was added or removed. A delivery rate above 100% means work was added mid-sprint and delivered.

7 · Cross-team roll-up

The Roll-up tab puts every team and the portfolio side by side, coloured against target. Needs attention lists teams that are off target or trending down, and Velocity by team compares rolling three-sprint velocity. This is the page to bring to a steering meeting.

8 · Trends over time

History arrives two ways. Imports with a date column (section 3, or Metric values with a Period column) fill in each month automatically. For figures you type in, record a snapshot:

1. On the Scorecard, choose the Snapshot period (month), e.g. September 2026.
2. Click Record snapshot. It captures every team and the portfolio at once.
3. Do the same each month or quarter. The Trends tab then charts each metric over time, and the scorecard shows the change since the previous snapshot.

Recording a snapshot for a period that already has one replaces it. Delete old snapshots at the bottom of the Trends tab.

9 · Export & share

Everything is under Export & share at the top right of the tool:

10 · Your data & backups

ReportInSite runs entirely in your browser. What you import or type is saved on your own device and is not uploaded. That means:

• Your report is there next time you open the tool in the same browser on the same computer.
• Clearing browser data, or using a private window, removes it. Back up (JSON) regularly, especially before clearing your browser.
• To work on another computer, back up on one and Restore from backup on the other.
• Clear data at the top of the tool removes everything, including framework changes, so you can start again. If you only want to remove your teams and sprints but keep your framework and targets, use Data → Start over instead.

More detail is on the Security & Data page.

11 · Troubleshooting

"No story points column found"

Your Jira export didn't include story points. Make sure you choose Export CSV (all fields), not "current fields". Issue counts and lead time still work without points.

The pasted Sprint Report adds nothing, or the numbers look wrong

Copy from Jira's Sprint Report page itself, starting at the "Completed Issues" heading, and paste without tidying it up. The tool relies on Jira's tab spacing.

"The file needs Area, Metric and Value columns"

You've chosen Metric values (CSV) for a sprint file. Use Sprint summary (CSV) or Jira issue export (CSV) instead, or start from the template.

Some metric values were "not in your framework"

The Area and Metric names in your CSV must match the Framework tab exactly. Download the template again to get the current names.

Committed doesn't match Jira

See the note in section 2: paste the Sprint Report for that sprint for exact figures.

My data has gone

Check you're in the same browser and not a private window. If browser data was cleared, restore from your last backup.

Open ReportInSite →