Skip to content
Workflow · Clean and combine · Opening soon

Jira issues to Excel with time logged against estimates

Export your Jira issues and load the file into Mammoth. It can add up original estimate, time logged, and remaining estimate from stories and sub-tasks, then put one row on the Excel output for each epic.

Early access opens shortly. Check back soon.

Someone typed

“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”

The agent read it as

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.

  1. File
    Jira issues
    CSV export · 45 rows
  2. Step
    Add up epic estimates and flag issues
    Step 1
  3. Result
    Jira Epic Estimates
    15 rows · 15 flagged
  4. Schedule
    Runs when you say
    Proposed

On the sample files, every step runs and the result has 15 rows.

What you get back

The result of that run, the rows to look at first.

Jira Epic EstimatesSample data15 rows
5 within estimate1 logged time over estimate7 not under an epic2 no estimate
Epic or issue keySummaryOriginal estimate hoursTime logged hoursRemaining estimate hoursStatus
APEX-102Mobile onboarding refresh000No estimate
APEX-108Knowledge base migration0200No estimate
APEX-206Login friction audit541Not under an epic
APEX-207Push token cleanup651Not under an epic
APEX-208Local cache warmup431Not under an epic
APEX-209Deep link fallback761Not under an epic
APEX-235Standalone research spike422Not under an epic
APEX-236Vendor list normalization321Not under an epic
APEX-237Sandbox access cleanup651Not under an epic
APEX-101Payments reconciliation50700Logged time over estimate
APEX-103Search relevance tuning38326Within estimate
APEX-104Checkout performance30264Within estimate
15 rows in the result · 12 shown, problems first. Sample data: illustrative figures, not business results.

How it works

How to use the Jira Epic Estimates workflow

  1. 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and working on sample files.
  2. 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
  3. 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?
Export your Jira issues and load the file into Mammoth. It can add up original estimate, time logged, and remaining estimate from stories and sub-tasks, then put one row on the Excel output for each epic. It can also flag epics where logged time is over the estimate, epics with no estimate, and issues that are not under any epic.
What Jira export should you use?
Use a Jira export that includes the issue fields you need, including epic links, estimates, time logged, and remaining estimate. If stories and sub-tasks matter, include them in the export too.
What happens to issues that are not under any epic?
They stay in the output as separate rows or flagged records, depending on the rule you set. You can filter or label them so they are easy to find in Excel.
How do you change the rules later?
You edit the rule words in the workflow, for example which fields to add up, which issues to group, and which conditions to flag. Then you run the same exported file again.

Get early access to this workflow

It opens already built and working on sample files. Swap in your own exports to see your result.

Early access opens shortly. Check back soon.