Sprint Pack help

Exports

Every export is built in your browser from the numbers you’re looking at, counted as you see them, and saved as a file. Nothing is sent anywhere.

Export Where What you get
Sprints, Issues, Estimate history (CSV) Sprint scope view One table per file
All three (Excel) Sprint scope view; per board in the portfolio One workbook
Download for slides Sprint scope view, sprint menu, widget, portfolio A .pptx with editable charts
Slide for one sprint Sprint scope view, sprint menu One slide: the sprint’s numbers and what changed
Show a summary to copy Sprint scope view, portfolio Plain sentences for email or chat
Share a snapshot Sprint scope view, portfolio A dated, self-describing .xlsx

CSV

Three files, each starting with the same four header lines:

  1. “As visible to you on "
  2. The board, the sprints included, the estimate field and unit, and the time zone
  3. “Definitions and caveats: ”
  4. Whether the file is complete: “Complete: every sprint shown is included.”, or a line starting “INCOMPLETE:” that names each sprint left out and why

The table always starts on line 5, under the row that begins sprintId. A script can skip the first four lines, or look for that row. Before using the data, check that line 4 starts with “Complete”.

A sprint the view shows as computing or updating is left out of an export until Sprint Pack has finished it, because exports carry finished numbers only. Line 4 names it; export again once it shows as up to date.

Then one table:

Dates carry your site’s time-zone offset. Time estimates are in hours (and seconds, in the Issues and History files).

If your Excel uses ; to separate values (common in Europe and Latin America), opening a CSV file puts each row in one column. Use All three (Excel) instead, or import the CSV with Data → From Text/CSV and choose comma as the delimiter.

Excel

All three (Excel) puts the Sprints, Issues and Estimate history tables in one workbook, plus a Definitions sheet: one row per column with its meaning and a link to its section of this help. The jql… columns are clickable links to Jira’s issue search.

In the portfolio, each board row has its own CSV (sprints) and Excel (all three) buttons. They export the sprints the row shows: the last N, or the sprints closed between the portfolio’s dates. The Excel file’s jql… columns are links, as in the Sprint scope view’s.

Download for slides

A .pptx built from the view’s numbers: one slide per board.

Slide for one sprint

One slide for a sprint review: the sprint’s numbers, then what changed and who changed it.

Copy summary

One plain sentence per sprint, from a fixed template, for email or chat. For example:

Sprint 14: committed 18 points, delivered 16 of them (88.9%); 5 points taken on and 2 removed after the start.

Snapshots

A snapshot is a dated, self-describing .xlsx you can send to someone else: it records what you saw, who it was counted as, and links that let them check every number live.

Sheets:

  1. Snapshot (the cover):
    • the board or boards, and the sprints covered;
    • a one-paragraph summary (the copy summary text) of the sprints in the file, with its date;
    • “Taken <date and time in the site’s time zone> ()";
    • “Counted as , who could see N issues; M issues on these sprints were hidden from them", and how many issues Sprint Pack itself couldn't see;
    • the app version and the counting rules’ version;
    • each sprint’s anomaly flags;
    • Check it live: for each sprint, a link to each bucket’s Jira search, so whoever opens the file can re-run the counts under their own permissions;
    • links to “How these numbers are counted” and “Why two people can see different numbers”.
  2. Sprints: the Sprints table, with anomalies and the jql… columns as links.
  3. Issues and 4. History: the same as the CSV exports.
  4. Definitions: one row per column and metric, with a link to its help.

People’s names appear where Jira records them: the assignee, who took on or removed an issue, who changed an estimate, and who wrote a reason. The Share group says so under its buttons. Think about who you send the file to, as you would with any Jira export.

Why two people can see different numbers: each count includes only issues the person counting could see. If the recipient’s “Check it live” link finds more or fewer issues, the difference is issues one of you can’t see, or changes since the snapshot was taken. See hidden issues.

Excel files have real, clickable links. CSV files can’t, so their links are plain text.

Apps the files haven’t been opened in

The vendor hasn’t yet opened the generated slides in PowerPoint, Keynote or Google Slides, or the generated workbooks and snapshots in Excel, Numbers or Google Sheets. They have been opened in LibreOffice, and their structure is checked by automated tests. If a file doesn’t open or looks wrong in one of these apps, please tell us.

Large exports and the hourly budget

The Sprints table always exports in full. The Issues and History tables read each issue from Jira as you, which counts against Sprint Pack’s hourly budget for views.