Anton from JetHeads_io Atlassian Partner

Hey Kate! 👋 The accuracy problem with task-switching is really a manual-overhead problem: every switch is a stop-here, start-there you have to remember, and the one you forget is where the day's numbers drift. The fix is taking that burden off people instead of leaning on discipline. That's what timers in JetTime (a…

I'm a developer of a JetTime time-tracking app, and we have a similar feature of custom time categories, but I really like your approach! Very lightweight and elegant. 👏

You can also push this to its limit: some work items shouldn't collect time at all. Point an empty scheme at an invoiced status or an epic, and logging simply stops there. Wrote that one up separately: ⏱️ How to turn off time tracking for specific Jira work items.

A concrete example of this, if you run client work: client-facing tasks can carry the client, a billing type, and a proper work description, while internal tasks get a stripped-down form with none of it. I walked through that setup step by step here: 🎛️ Customize the Jira Log Work form per project, client, or work item.

If you want to take this further, the same rules can also switch the Log Work form off completely — for work items that shouldn't collect time at all, like an invoiced status or an epic container. That one's here: ⏱️ How to turn off time tracking for specific Jira work items.

Worth adding: the same Field Schemes engine works the other way round too — shaping which fields appear and which are required per work item. I covered that side separately here: 🎛️ Customize the Jira Log Work form per project, client, or work item.

That's fair, and Tempo's a solid, mature tool — licensing every user is really just how most Marketplace apps are priced, ours included. Where JetTime (the app from my other reply here) can help on budget: it's free for teams up to 10 users. Above 10 users, it's one of the most cost-effective options you'll find on the…

Hey Barbara! 👋 The others are right that native Jira can't log work for someone else — and the attribution point you raised is the real catch. Service accounts or logging in as someone else all park the hours under the wrong name. That exact gap is what JetTime (a third-party Jira app) closes. * Log work for any employee,…

Hey Adam! 👋 That install error is on the vendor's side, like Nikola said — nothing on your end to fix, so an actively-maintained alternative is the practical way forward. Turning worklogs into invoice-ready reports is exactly what JetTime (a third-party Jira app) is built for. * Split hours into your own time categories —…

Hey Rafal! 👋 When "see everyone's time" suddenly drops to "just my own," it's almost never your Jira permissions — it's a visibility layer inside the app itself. Hempel's pointer above is the right first stop: Time Tracker gates other people's entries behind its Auditor Groups setting, and since Tempo now owns the app,…

Hey Shivoy! 👋 Native Jira only rolls time up one level — a Sub-task into its direct parent, and that's where it stops. Nothing carries the hours further up through Story → Epic → Milestone, so the higher you look, the emptier it gets. That full multi-level roll-up is exactly what JetTime (a third-party Jira app) does. It's…

Hey James! 👋 You've actually got two separate problems tangled together here, and they're easier to solve once you split them. 1. Jira-to-Jira sync (the source-of-truth side). This is its own thing — mirroring the agency's issues into your instance so your team has something local to work against. There are solid…

Hey @Anna Patrizia Molero! 👋 That blank spot is the giveaway: installing a Timesheet app registered it as your site's time tracking provider, so Jira swapped the native Log work field for that app's own widget — and if the widget isn't loading in your new space, you get the empty screen instead of the field. Gabriela's…

Hi @tapan! 👋 The Workload Pie Chart gadget Trudy pointed you to is a solid quick win — it'll give you that grand total of time spent grouped by assignee right on a dashboard. Where it stops is detail: it's a single snapshot pie, so there's no real date range, no per-user table you can read row by row, and nothing to export…

Quick follow-up on this 👋 Last week we shipped the full roll-up I mentioned — so that single-level limit is gone. In JetTime, a month-wise total for an epic now includes everything nested under it — its stories and their sub-tasks — rolled all the way down, not just the direct children. So you can group by epic, break the…

Hey @Barbara Homer! 👋 Hopping between tickets just to log a few minutes each is one of the things native Jira makes harder than it should be — there's no single place to log everything and see your own totals. That's the first thing JetTime (a third-party Jira app) gives you: a My Work page that's your one screen for…

Hey @Avijit Nath! 👋 Native Jira time tracking only keeps one running total per issue — there's no built-in way to slice that logged time by month, or to see a month-by-month view across an epic and its stories. That's the gap JetTime (a third-party Jira app) fills — you build a report, group it by Parent, and break the…

Hey @Antun Štefančić! 👋 Yeah, native Jira only shows time logged per issue — there's no built-in way to see total hours someone worked across a month or across projects. JetTime (a third-party Jira app) handles this — you can generate reports showing total hours per user over any period (e.g., a full month), broken down by…

Hey @Rafael Marin! 👋 Native Jira dashboards struggle with this kind of aggregated time reporting — that's why your attempts probably came back with wrong or incomplete totals. JetTime (a third-party Jira app) does this through saved reports rather than dashboards. You can build a report showing total time per user over a…

Hey @Lucas Reis! 👋 A Marketplace app is the way to go for this. JetTime (a third-party Jira app) handles exactly this — it has a dedicated Timers page where you pick an issue and start the timer in one click, and timers are also available right on each issue. Either way, start/pause/stop a live timer and it logs the…

Hey @Anna Holovko! If Time Tracker isn't showing up or loading, first check with their support team — it could be a permissions issue or a bug on their end. If it's still not working, you might want to consider JetTime (a third-party Jira app) as an alternative or temporary solution while they fix it: * Time tracking &…

Hey @Abhishek Tiwari! Best bet is to contact the Time Tracker support team directly — they'll be able to troubleshoot this faster and check if it's a server issue or config problem on their end. If you need a temporary solution while they fix it, JetTime might work — it has time tracking with timers, timesheets, and…

Hey @daniel.billingham! Native Jira doesn't let you display Work Description from worklogs on dashboards — that field is only accessible inside the issue itself. JetTime (a third-party Jira app) might help here — you can add custom worklog fields (like "Waste Type" or "Reason") to categorize time entries, and then generate…

Hey @Natalie Keane! Thanks for asking this question!)) Tempo is solid and popular, but "best" is subjective — it's feature-packed, which is great if you need all of it, but can feel like bringing a sledgehammer to hang a picture frame if you just want clean time tracking and reports. If you're curious about lighter…

Hey @Mahesh Gupta! Best bet is to contact the App Time support team directly — they'll be able to troubleshoot this faster and check if it's a data loading issue or a bug on their end. If you're open to trying an alternative while they fix the bug, JetTime (a third-party Jira app) might work as a temporary solution — it…

Hey @Devakumar! Native Jira doesn't have a built-in weekly timesheet view — you'd need a third-party app for that. JetTime can do this — generate weekly timesheet reports with day-by-day breakdown, filter by user or project, and admins can see all reports across the team. You can also export to Excel or PDF. JetTime…

Hey @Laura Fallon! Native Jira doesn't let you filter worklogs by the date they were logged — it only shows total time per issue, not broken down by month. JetTime (a third-party Jira app) can do exactly this — generate a timesheet report filtered by date range (e.g., January 2026) showing all worklogs and/or work items…

Hey @Cris Dunn! Native Jira doesn't let you transfer worklogs between users or log time on behalf of someone else directly — you'd have to delete and re-create the worklog manually, which is painful. For a marketplace app, JetTime can help with this — you can give specific users permission to manage worklogs and track time…

Hey @jason.roberts! Native Jira filters and gadgets don't handle worklog and comment filtering by date range well — they either show everything or nothing useful for digest-style reporting. For the worklog part, JetTime (a third-party Jira app) can help — you can generate timesheet reports filtered by date range (e.g.,…

Hey @RenukaPrasad R! 👋 JetTime is a third-party time tracking app that can do exactly this — group by users (Y-axis) and enable timesheet mode with day-by-day breakdown (X-axis). It'll show each worklog entry separately per day, not aggregated, so you'll see User A's 2 hours on 1-Nov, 4 hours on 22-Dec, and 2 hours on…