Team Pivot Gadget for Jira — User Manual

1. What this gadget shows

Team Pivot shows the issues of a saved filter or a JQL query in one table:

• a row for each Team that has issues in the filter,
• a column for each value of a field you pick,
• in each cell, a count of issues or a sum of story points.

Rows and columns have totals. Select any number to open those issues in Jira's search.

It writes nothing to Jira, and it sends no data outside Atlassian.

2. Setting it up

1. Open a dashboard and choose Add gadget.
2. Add Team Pivot Gadget for Jira.
3. In the gadget, choose where the issues come from: a saved filter, or a JQL query.
4. Pick the field for the columns, and issue count or story points for the values.
5. Select Show table.

The gadget remembers its settings. Each gadget keeps its own, so two gadgets on the same dashboard can show two different tables. To change them later, select Settings.

3. Reading the table

3.1 Rows: Teams

Each row is a Team from Jira's Team field. Issues that have no Team are not dropped: they get their own row, (no Team), at the bottom.

3.2 Columns

You can pick one of these fields for the columns: Status, Status category, Issue type, Priority, Assignee, Sprint, Fix version, Component, Label.

Issues with no value in that field get their own column, (none).

Statuses and issue types with the same name are one column. In Jira, every team-managed project gets its own copy of statuses like To Do — same name, different status. If your filter covers several projects, you see one To Do column, not one per project. Sprints, versions and components are not merged this way: two sprints with the same name are still two different sprints.

3.3 Values: issue count or story points

• Issue count — how many issues are in the cell.
• Story points — the sum of the issues' story points.

In story points mode, an issue with no estimate is not counted as zero. It is left out of the sums, and the gadget tells you how many issues had no estimate. A cell whose issues have no estimate at all shows –.

3.4 Totals

The Total column and the Total row count each issue once.

For single-value fields, like Status, that is simply the sum of the cells. For fields that can hold several values — Sprint, Fix version, Component, Label — one issue can sit in several cells of its row, and the total is then smaller than the sum of the cells. The gadget reminds you of this when you pick one of those fields.

3.5 Sorting

Sort the rows by Team name or by Total, above the table. By Team name, the (no Team) row comes last; by Total, it moves like any other row. The Total row always stays at the bottom.

3.6 Opening the issues

Select any number — a cell, a row total, a column total or the grand total — to open Jira's issue search with exactly those issues. From there you can use everything Jira's search offers, including export.

4. What we can and cannot see

Issues you cannot see

The app asks Jira with your permissions. If an issue is hidden from you, it is not in your table — and we cannot flag this, because a hidden issue looks exactly the same to us as an issue that does not exist. Two people looking at the same gadget can see different numbers.

Large filters

The gadget counts up to 3,000 issues per table, and it has a time limit. If a filter is bigger, or Jira answers slowly, the gadget stops, says so, and marks every number with ~. A number marked ~ is lower than the real total. Narrow the filter to see everything.

Queries that point at nothing

If your JQL names a field, a project or a value that does not exist, Jira's search returns no issues and no warning. The gadget then says "No issues match" — and offers to open the query in Jira's issue search, which does tell you what is wrong.

If a saved filter was deleted, or is no longer shared with you, the gadget says that instead.

The Team field

The table needs Jira's Team field. If your site has none, the gadget tells you so, and there is no table to show.

Story points

The app uses Jira Software's story point estimate field. It finds it by its type, not by its name, so renaming the field does not matter.

A separate number field that someone created and named "Story Points" is not used: to Jira, it looks the same as any other number field, and guessing by name would sometimes pick the wrong one. If the gadget finds no story point field, it says so and shows issue counts.

Sub-tasks

Sub-tasks that match your filter are counted like any other issue — the same way Jira's own search counts them. If you want them left out, add AND issuetype not in subTaskIssueTypes() to your query.

5. Frequently confusing things

5.1 "The total is smaller than the sum of the cells"

You picked Sprint, Fix version, Component or Label. An issue with two sprints is in two cells, but it is still one issue. See section 3.4.

5.2 "The numbers are different from yesterday / from my colleague's"

The table is built fresh each time from Jira's current data, with the viewer's permissions. See section 4, Issues you cannot see.

5.3 "Some issues have no story points, but the cell shows a number"

The cell adds up the estimates it has, and the warning above the table says how many issues had none. An issue without an estimate is not a zero.

5.4 "There is only one To Do column, but my projects each have one"

Statuses with the same name are merged into one column. Selecting a number still opens exactly the right issues. See section 3.2.

6. Permissions the app asks for

The app has no write permission. It cannot change anything in Jira.

About read:jira-work. On the install screen Jira calls this one "View Jira issue data", and describes it as reading project and issue data, searching for issues, and objects like attachments and worklogs. That is Jira's wording for the whole permission, not a list of what this app does.

This app never reads attachments, comments or worklogs. For each issue it asks only for the fields the table needs: the Team, the field you picked for the columns, and the story points.

7. Data and privacy

The app searches Jira through Atlassian's own API, with your permissions. It writes nothing back, and it makes no network calls outside Atlassian. It stores only each gadget's settings, on Atlassian's app storage — including the JQL query, exactly as you typed it. Remove the app and Atlassian soft-deletes the settings straight away, then erases them after its own retention period.

[ Full privacy statement → ]

8. Getting help

Email: support@axerilabs.com

We reply within two working days. Written support in English.

If Atlassian classifies an issue as critical, we reply within 24 hours, weekends included. A reply means we have read your report and told you what happens next. It does not mean the fix is ready: we do not promise a fix time.

We do not offer phone, video or live chat support.

If a number looks wrong, please read sections 4 and 5 first. If your case is not there, write to us: tell us the filter or query, the field you picked for the columns, and what you expected to see.