TimeEase · 2026

Introducing Issue Insights: Know Where an Issue Stands, Without Leaving It

Sep 10, 2026  ·  6 min read  ·  TimeEase Team

Open almost any Epic or Story in Jira and you'll find an Original Estimate field, a Time Spent field, and not much else. If the issue has sub-tasks, Jira's own aggregate fields try to roll those numbers up — but only work cleanly through proper sub-task relationships, and fall apart the moment a hierarchy uses Epic/Story links or spans more than one level. And nowhere in the issue view does Jira tell you who actually logged that time.

Issue Insights is a new, read-only panel in the Jira issue sidebar that answers both questions at once: how is this issue tracking against its estimate — including everything underneath it — and who's been doing the work. It's live now, right where you're already looking.

The Problem: The Issue View Has No Reporting Surface

TimeEase already puts time tracking inside the issue view in two places — the Stopwatch gadget for a raw worklog list, and Quick Log Time for fast entry. Neither was built to answer "are we on budget, and who's logged the hours":

  • The Stopwatch gadget shows a flat worklog list for the current issue only — no estimate, no remaining, no per-person totals
  • Quick Log Time is built for entry, not reporting — there's nothing to look at once time is logged
  • Rolling up time across an Epic's children only existed in the project-level Feature Analytics dashboards — useful, but a context switch away from the issue you're actually looking at
  • Jira's native aggregatetimespent and aggregatetimeoriginalestimate fields quietly under-report the moment your hierarchy isn't a strict, single-level sub-task tree

What Issue Insights Shows

Open any issue and the panel renders a small grid of stat tiles — Estimate, Remaining, Logged, and, on the Advanced edition, Cost — each with its own icon and a large, glanceable number. Underneath sits a progress bar showing percentage of estimate consumed, and a Collaborators list of everyone who logged time, sorted by how much they logged.

  • Rolled up, not just local: for an Epic or Story with children, every tile includes time from sub-tasks, grandchildren, and great-grandchildren — computed the same bottom-up way TimeEase's Feature Analytics dashboards already do, by summing each issue's own fields directly rather than trusting Jira's aggregate fields
  • A visible marker when a number is rolled up: tiles that include sub-issue data carry a small linked-items icon next to their label, so you always know whether you're looking at just this issue or the whole hierarchy underneath it
  • Overspent, shown honestly: if remaining estimate goes negative, the panel reads "Over by Xh" instead of a confusing negative number, and the progress bar fills in a warning color instead of silently breaking past 100%
  • Deviation, at a glance (Advanced): a lozenge next to the progress bar flags how far actual logged time has drifted from estimate, using the same ±20% / ±40% bands as TimeEase's existing Estimation Insights tab

Collaborators: Who Actually Logged the Time

Below the summary, every worklog author across the issue and its rolled-up descendants is merged into one list — avatar, name, and total time logged, most active first. Click a name and it opens that person's Jira profile in a new tab.

It's not a list of who's assigned or who's watching — it's specifically who put in logged hours, which is the question a manager or client actually has when looking at where an Epic's time went.

Always Live, No Dashboard to Refresh

Issue Insights runs entirely synchronously — there's no background job, no cache, no "recalculate" button. Every time you open the panel, it fetches the issue, its descendants, and their worklogs fresh and computes the numbers on the spot. Nothing to wait on later, nothing to go stale between visits.

For genuinely large Epics — hundreds or thousands of descendants — the panel is honest about the tradeoff that comes with staying synchronous: it works through the hierarchy breadth-first and, if it runs out of time before finishing, shows a clearly labeled "partial results" banner rather than an eventual-but-delayed complete number. For that kind of exhaustive rollup, TimeEase's project-level Feature Analytics dashboards remain the right tool — Issue Insights is built for a fast, honest glance at the issue in front of you, not a full audit.

Who This Is For

  • Engineering leads: check an Epic's budget tracking mid-sprint without opening a project dashboard
  • Anyone managing work split across sub-tasks: get a real rolled-up number instead of Jira's aggregate fields, which only work under strict sub-task hierarchies

Getting Started

  1. Open any issue in Jira with TimeEase installed
  2. Look for Issue Insights in the right-hand sidebar
  3. Estimate, Remaining, Logged, and Collaborators load automatically — no setup required

💡 Note: Issue Insights is available on any active TimeEase plan. Cost and Deviation are Advanced edition features, visible only to teams with that access enabled.

Try Issue Insights today

TimeEase is free to try and installs in seconds from the Atlassian Marketplace. Open any issue and Issue Insights is already there.

Install TimeEase Free →

Available for Jira Cloud · Forge-native · Free tier available

Published: Sep 10, 2026