If you read our last post, you know the problem: Jira's Original Estimate field holds one number, from one edit — which falls apart the moment more than one person needs to contribute to it. Here's what that looks like solved, step by step, inside TeamTime.
A quick note on where this fits: TeamTime already gives you cumulative mode (roll estimates and time up through the full hierarchy) and distributive mode (track a fixed hour budget across linked tickets). CumulativePlus is a third mode, for when several people are estimating the same ticket and you need to see each person's share — not just the total.
The scenario
A designer, a frontend developer, and a backend developer all pick up pieces of the same user story in a sprint. Each of them needs to estimate their part. Here's how that goes with CumulativePlus turned on.
Step 1: Everyone just logs their own estimate
There's no setup step required before anyone can contribute. Each person opens the ticket, adds their own estimate with a short description of what it covers, and saves it.
The moment someone submits an estimate, they're automatically included as a co-assignee on the ticket — even if they're not the primary Jira assignee. A manager can also add people manually ahead of time, from the co-assignee field, if they want the full team visible on the ticket before anyone has estimated anything. Either way works; nobody has to be added first for their estimate to count.
Step 2: Every estimate is logged, not just added to a total
Each estimate shows up in the ticket's Estimate log, right next to Jira's native work log — who added it, how much, and when.
If someone needs to correct their own number later, they can edit it themselves — no need to ask an admin. A Space Admin can also edit or delete anyone's estimate if something needs fixing after the fact, and every change keeps a visible edit history, so nothing disappears silently.
Like TeamTime's cumulative mode, CumulativePlus totals a ticket's own estimate together with its children's. If a ticket already has its own estimate and its contributors also log individual estimates on it, those get added together — so it's worth agreeing as a team whether estimates live on the parent, on individual entries, or consistently one or the other, the same way you would with cumulative mode.
Step 3: See the breakdown, not just the total
Once estimates are in, you can see them broken down by person in two ways: turn on "Show user estimates" right inside your normal report to see per-person entries under each ticket, or switch the whole report to group By users instead of by work item — which flips the view so each team member becomes the main row, with their tickets grouped underneath.
If your team has used Jira's Version Workload Report to check who's carrying how much load in a sprint or release, this gives you a similar breakdown — built natively into your existing TeamTime reports, without a separate tool.
What this changes, depending on your role
For team leads and delivery managers: you see exactly who's carrying the load in a sprint or release, without pinging people to ask.
For individual contributors: you add your own estimate once, on your own terms — no waiting on someone else to update a shared number, no risk of your part getting overwritten.
For anyone accountable for the numbers: the total is always built from real, timestamped entries — not whoever did the mental math last.
Try it with your team
CumulativePlus is part of TeamTime's Advanced Tier. Atlassian gives every Jira site a free 30-day trial of Advanced — whether you're new to TeamTime or already using Standard.
You can find TeamTime, with pricing and trial details, on our Atlassian Marketplace listing.
