Jira issues to Excel with time logged against estimates
“export our jira issues to excel one row per epic with the original estimate, time logged and remaining estimate added up from its stories and sub-tasks, and flag epics where logged time is already over the estimate, epics with no estimate, and issues that are not under any epic”
Export our Jira issues to Excel one row per epic with the original estimate, time logged and remaining estimate added up from its stories and sub-tasks, and flag epics where logged time is already over the estimate, epics with no estimate, and issues that are not under any epic.
What the agent built
1 step, each one an ordinary Mammoth step you can open and change.
- FileJira issuesCSV export · 45 rows
- StepAdd up epic estimates and flag issuesStep 1
- ResultJira Epic Estimates15 rows · 15 flagged
- ScheduleRuns when you sayProposed
On the sample files, every step runs and the result has 15 rows.
- Download Jira issues sample (45 rows)Jira: Issues > Search issues > Export > CSV (open in Excel)
What you get back
The result of that run, the rows to look at first.
| Epic or issue key | Summary | Original estimate hours | Time logged hours | Remaining estimate hours | Status |
|---|---|---|---|---|---|
| APEX-102 | Mobile onboarding refresh | 0 | 0 | 0 | No estimate |
| APEX-108 | Knowledge base migration | 0 | 20 | 0 | No estimate |
| APEX-206 | Login friction audit | 5 | 4 | 1 | Not under an epic |
| APEX-207 | Push token cleanup | 6 | 5 | 1 | Not under an epic |
| APEX-208 | Local cache warmup | 4 | 3 | 1 | Not under an epic |
| APEX-209 | Deep link fallback | 7 | 6 | 1 | Not under an epic |
| APEX-235 | Standalone research spike | 4 | 2 | 2 | Not under an epic |
| APEX-236 | Vendor list normalization | 3 | 2 | 1 | Not under an epic |
| APEX-237 | Sandbox access cleanup | 6 | 5 | 1 | Not under an epic |
| APEX-101 | Payments reconciliation | 50 | 70 | 0 | Logged time over estimate |
| APEX-103 | Search relevance tuning | 38 | 32 | 6 | Within estimate |
| APEX-104 | Checkout performance | 30 | 26 | 4 | Within estimate |
How it works
How to use the Jira Epic Estimates workflow
- 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and working on sample files.
- 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
- 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.
Jira Epic Estimates: questions
How do you export Jira issues to Excel with time logged against estimates?
What Jira export should you use?
What happens to issues that are not under any epic?
How do you change the rules later?
Get early access to this workflow
It opens already built and working on sample files. Swap in your own exports to see your result.
Workflows like this
Remove duplicates, tidy names and addresses, fill the blanks, and merge files into one.
- Pivot table from raw dataTurn a raw sales export into a pivot table of revenue by region and month.See the workflow Built by the agent
- Merge Excel or CSV filesOne tidy table with every file's rows, re-sent rows dropped, and a Period columnSee the workflow Template
- Remove duplicatesOne row of each, with a Copies column saying how many there wereSee the workflow Template
- Remove blank rowsRemove rows that are empty or only contain spaces from an Excel export, while keeping the rest of the sheet unchanged.See the workflow Built by the agent
- Match names to a master listEach record with its master name (and ID), and how it matchedSee the workflow Template
- Multi-entity consolidationEvery entity's balances in one currency, by accountSee the workflow Template