How can I measure non-cumulative time spent by engineers across multiple Jira tickets?

[Robert]

Hi everyone 👋

I’m trying to set up a clear time-tracking view in Jira that shows how much time each engineer spends working on tickets — but without double-counting overlapping workdays.

For example, if an engineer works on Ticket A from Nov 1–3 and Ticket B from Nov 2–3, Jira should show that they were active for 3 business days total, not 5.

I’ve already tested a few marketplace apps (Timepiece, Time in Status, etc.), but most of them only provide cumulative time reports.

Is there any way — through automation, custom JQL, or a marketplace app — to calculate distinct working days per engineer, ideally grouped by Epic?

Any recommendations or creative setups would be awesome 🙏

Thanks in advance!

[Trudy Claspill]

Hello @Robert 

Your question is very similar to the questions posted by @mborinstein . Have you seen those? You may want to review the feedback that member has received.

https://community.atlassian.com/forums/Jira-questions/Counting-of-Days-spent-per-Engineer-in-an-Epic/qaq-p/3137904

https://community.atlassian.com/forums/Jira-questions/Best-time-tracking-app/qaq-p/3140310

[Paul Glantschnig - JXL]

Hi @Robert ,

If you are generally open to Atlassian Marketplace suggestions, you may want to have a look at the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your Jira data that allows viewing, inline-editing, copy-pasting, sorting, and filtering by all your work items' fields, much like you’d do in e.g. Excel, Google Sheets, Smartsheet, or Airtable. It also comes with a long list of further features, including work item grouping based any work item fields, as well as sum-ups.

With these, you can build a view like e.g. this in just a couple of clicks:

This is really just one of a virtually endless number of possible views and reports; you can also view and group by any other issue fields, configure different sum-up styles, etc. etc. I should also add that JXL can do much more than the above: From configurable issue hierarchies, to conditional formatting, or inline bulk editing via copy/paste.

Any questions just let me know,
Best,

Paul