Datum

Docs → Tally

Documentation · Jirav2.7.1

Tally docs

Tally rolls status, count and % done up from every child issue and sub-task to the parent, through every level and across projects. It shows the rollup in the Tally — Rollup issue panel, in the Tally — Epic Rollups dashboard gadget, and stores it on the issue so you can search and sort on it in JQL.

Getting started

Before you install

  • Jira Cloud. Tally is a Forge app (Runs on Atlassian).
  • A Jira admin to install the app and approve its two scopes (read:jira-work, write:jira-work).
  • Story Points and time rollups need the Standard plan. Story Points are read from the company-managed Story Points and team-managed Story point estimate fields; time comes from Jira time tracking (original estimate, time logged, remaining).

Install and first use

  1. Install the appInstall Tally from the Atlassian Marketplace. Nothing to configure: there are no formulas or field mappings. On install, a background rebuild starts storing a rollup on every issue that has children, so JQL covers your existing epics too.
  2. Open the rollup on an issueOpen an epic or any parent issue and add the Tally — Rollup panel from the app buttons in the issue view. It shows how many child issues are To do, In progress and Done, plus the % done for the whole tree below the issue.
  3. Search and sort in JQLUse the rollup in any filter, e.g. issuetype = Epic AND tallyPercent < 50 ORDER BY tallyPercent. On Standard you can also sort by time, e.g. ORDER BY tallyRemainingHours DESC.
  4. Add the dashboard gadgetOn a Jira dashboard, choose Add gadget and pick Tally — Epic Rollups. Until you set a query it shows open epics (issuetype = Epic AND statusCategory != Done ORDER BY rank). Use the gadget's Edit menu to enter your own JQL, optionally pick Group by (assignee, status category, project, labels, components, fix versions, or a select, checkbox, user-picker, short-text or labels custom field) and tick Add To Do / In progress / Done columns for a status breakdown per group, then click Save. With a field that holds several values, an issue counts once in each of its groups.
  5. Check the background rebuild (admins)Go to Jira settings → Apps → Tally — Rollups to see the rebuild's progress. Click Rebuild rollups now to run it again, or Refresh status to update the view.
  6. Ask RovoIf your site has Rovo, open the Tally Progress agent or ask Rovo chat How far along is PROJ-12? It answers with % done and done / in progress / to do through every level, lists the least-done parents for any JQL, and finds late epics. On Standard it adds story points, time and epics whose children are due after the epic. Counts only include issues you can see.

Configuration

How the rollup is counted

Every issue below the parent counts once, by its status category: To do, In progress or Done. % done is the share of issues in the Done category. It reads 100% only when everything is done and 0% only when nothing is; anything in between is shown as 1–99%, so 199 of 200 reads 99%, not 100%.

Child issues in other projects are included, because Tally follows the parent link rather than a project.

Standard: points and time

  • Story Points done / total and % done by points. Sites that use both the company-managed and team-managed points fields are added up correctly.
  • Original estimate, time logged, and remaining time (remaining counts open issues only).
  • A count of open items with no estimate: open issues with no Story Points and no original estimate on themselves, an ancestor or a descendant.
  • Sums of up to 3 number custom fields chosen by a Jira admin on Tally — Rollups.
  • A date rollup: the earliest start date and the latest due date across the tree. The end field is Due date until an admin picks another date field (and, optionally, a start date field) under Date rollup on Tally — Rollups. Saving starts a background rebuild.

Gadget group-by

In the gadget's Edit view, set Group by to Assignee, Status category or Project. The gadget then shows one row per group with the number of matching issues and how many of their child issues are done. Standard adds Story Points, remaining time and the latest due date per group.

Grouping adds up the rollups already stored on the matching issues (the first 500 matches), so an issue without children, or one not yet computed, counts as an issue with no child issues.

JQL fields

Tally stores the rollup on the parent issue as the tally-rollup issue property. Jira indexes it so these fields work in JQL with = != > >= < <= and ORDER BY.

  • Free and Standard: tallyPercent, tallyDone, tallyTotal, tallyOpen, tallyUpdated (date of the last rollup).
  • Standard only: tallyPoints, tallyPointsDone, tallyPointsPercent, tallyEstimateHours, tallySpentHours, tallyRemainingHours, tallyUnestimated, tallySum1–tallySum3, and the dates tallyEarliest and tallyLatest (for example tallyLatest > endOfMonth()).
  • A value with no data is left out rather than stored as 0, so tallyPoints is EMPTY means no points data.

Keeping rollups current

When an issue is created, edited or deleted, Tally recomputes the stored rollup of each of its ancestors. If an issue moves to a new parent, the old parent is refreshed too.

The issue panel computes the rollup live each time you open it. The gadget recomputes any row whose stored rollup is missing, more than a day old, or was written on the other plan.

An hourly check starts the background rebuild if it never ran and resumes it if it stopped. Only Jira admins can see the admin page or start a rebuild.

Charts and insights

The Tally — Epic Rollups dashboard gadget draws a To do / In progress / Done bar per group, or % done for the least-done issues, and the issue panel shows a To do / In progress / Done bar for the whole tree. Standard adds a story points done vs remaining chart per group.

Language

Available in English, German, French and Spanish. The app follows each person's Jira language setting; Rovo answers, exports and comments the app posts stay in English.

Free vs Standard

Plans and prices below are read from the same pricing file the app uses. Atlassian bills per user per month on your site's user tier, and the price per user steps down at larger tiers. See all pricing.

Free

Free

  • Status, count and % done for the whole tree (every level, across projects)
  • Rollup searchable and sortable in JQL, plus a dashboard gadget
  • Gadget group-by: rollups per assignee, status category, project, label, component, fix version or custom field

Standard

$0.75 / user / month

Free for sites up to 10 users. 30-day free trial.

  • Story Points rollup (company- and team-managed fields)
  • Original estimate, time logged and remaining time
  • Open items with no estimate, flagged
  • Date rollup: earliest start and latest due date across the tree, searchable in JQL (tallyEarliest / tallyLatest)
  • Points, remaining time and latest due date per gadget group

Limits

  • The issue panel walks up to 6 levels below the issue and up to 2,000 issues, within about 18 seconds. Background refreshes and the rebuild allow up to 5,000 issues per parent.
  • If not every issue could be read in time, the panel shows a Very large hierarchy warning and the numbers are a minimum, not the full total. The gadget marks such rows as partial.
  • The dashboard gadget shows the first 20 issues that match its JQL; grouped, it adds up the first 500.
  • On a change, ancestors are refreshed up to 6 levels up.
  • Free stores and shows status, count and % done only. Story Points, estimates, time and the unestimated count need Standard; on Free those JQL fields are empty.
  • Custom fields: Standard sums up to 3 number fields and rolls up one start and one due/end date field. No formulas, select or Assets fields, board column or new custom field.

Data & privacy

What Tally stores

  • Each parent issue's rollup is stored as the tally-rollup issue property inside your Jira site: counts (total, done, open), % done, the plan it was computed on, a partial flag and a timestamp. On Standard it also holds points, estimate, time logged, remaining hours, the unestimated count, the custom field sums and the earliest / latest date.
  • The background rebuild's progress is stored as a Jira app property (tally-backfill) on your site, and the admin's field choices as tally-custom-sums and tally-date-rollup.
  • No names, account IDs or issue content are stored. Tally never edits issue fields; its only write is its own rollup property.
  • The manifest declares no external hosts, so no data is sent outside Atlassian.

Tally runs on Atlassian Forge. Data it stores sits in Forge hosted storage for your site, which Atlassian pins to your product's region. See Trust & security, the Privacy Policy and the DPA.

Permissions (scopes)

ScopeWhy Tally needs it
read:jira-workRead child issues, their status, Story Points and time tracking to compute the rollup, and run the gadget's JQL search.
write:jira-workStore the computed rollup as the tally-rollup property on the parent issue so it is searchable in JQL. It never edits issue fields.

FAQ & troubleshooting

My JQL search on tallyPercent returns nothing. Why?

A rollup is stored only on issues that have children, and only after the background rebuild, a change to a child, or someone opening the issue. Check the rebuild under Jira settings → Apps → Tally — Rollups and click Rebuild rollups now if it did not finish. Searching on tallyPoints or the hours fields needs Standard; on Free those fields are empty.

The percent looks wrong or out of date.

The issue panel always computes live, so open the issue to get current numbers; that also updates the stored value used by JQL. % done counts issues by status category, so an issue in a status Jira files under Done counts as done. It shows 99% until every issue is done, and 1% as soon as one is.

Why does the gadget say a row is "Not computed yet"?

That issue has no stored rollup yet and the gadget ran out of time computing it during this load. Reload the dashboard shortly. A row reading "No child issues" has nothing below it to roll up.

Does it include child issues in other projects?

Yes. Tally follows the parent link through every level, so children in other projects are counted.

Why are my Story Points missing?

Points and time need the Standard plan. Tally reads every custom field named like Story Points or Story point estimate; if your site has no such field, or no child has a value, the points line is hidden.

What does the "Very large hierarchy" warning mean?

The tree was too big to read within the time limit, so some issues were not counted. Treat the numbers as a minimum. Very large trees are read within a time budget instead of showing a wrong total silently.

Who can see the gadget's results?

The gadget runs its JQL as the person viewing the dashboard, so it only lists issues they can browse.

Changelog

Every release and what changed: Tally changelog.

Getting help

Email support@datadir.co with your site URL and what you saw. Our target is a first response within 1 business day. See Support for what to include, and Status for known issues.