Free tools Windows power users keep installed
One-click scans. No signup required.
If your team uses Tempo Timesheets on Jira Cloud, Jira may record a Tempo app account—not the person who entered the time—as the worklog author. In that case, Jira’s native worklogAuthor = currentUser() search cannot identify that individual. Check the Tempo panel on the issue, the Tempo Logged Time Report, or Tempo’s REST API for Tempo worklog details. On Jira Data Center 9.0 and later, a separate issue can also hide matches: JQL indexes only the 100 newest worklogs on each issue.
First, identify which Jira setup you have
The empty result can have different causes depending on where Jira is hosted. Check the worklog author displayed in Jira, the affected issue’s worklog count, and—if you use Data Center—whether the target worklog is among the issue’s 100 newest entries.
As an Amazon Associate I earn from qualifying purchases.
| What to check | What it may indicate | Next step |
|---|---|---|
| Jira Cloud; Jira shows “Timesheets by Tempo – Jira Time Tracking” as the author | Tempo’s Cloud worklog representation may be anonymized under its app user. | Inspect the worklog in Tempo’s panel, Logged Time Report, or REST API. Tempo explains the Cloud behavior and these routes. |
| Jira Server or Data Center 9.0 or later; issue has more than 100 worklogs | The target entry may be outside the worklogs Jira indexes for JQL. | Check the entry’s recency and the Jira version. Atlassian documents the indexing limit. |
Jira Cloud: Tempo may be the Jira-visible author
Tempo says it operates as an independent system on Jira Cloud, with its own database, and manages synced worklogs through a Tempo app user. Jira may therefore display “Timesheets by Tempo – Jira Time Tracking” rather than the person who logged the time. Tempo says Jira’s REST API returns anonymized Tempo worklog data and JQL searches using worklogAuthor will not identify specific individuals.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOpen an affected issue and compare Jira’s worklog entry with the Tempo panel or report. If Jira attributes the entry to the Tempo app while Tempo identifies the person, the Cloud anonymization explanation fits. Access to view other people’s worklogs in Tempo may depend on your permissions.
Where to inspect the full Tempo record
- Open the issue’s Tempo panel.
- Use Tempo’s Logged Time Report.
- For an integration, query the Tempo REST API.
These are the documented places to inspect Tempo worklog details; changing the Jira JQL expression does not reveal an individual identity that Jira has received in anonymized form.
Data Center 9.0+: check the per-issue indexing limit
Atlassian says Jira Server and Data Center from version 9.0.0 index only the 100 most recent worklogs on an issue. If an issue has more than 100 worklogs and the person’s entry is older than the newest 100, a JQL search using worklogAuthor or worklogDate can miss that issue. Atlassian’s support article, updated September 26, 2025, also lists safeguards of 500 comments and 100 change-history entries; the relevant limit here is 100 worklogs per issue.
Rank #2
Checks before changing configuration
- Confirm that the instance is Jira Server or Data Center and is on version 9.0.0 or later.
- Check whether the symptom started after an upgrade from Jira 8.x.
- Check whether the affected issue has more than 100 worklogs and whether the target entry falls outside the newest 100.
Administrator-only workaround
For this specific indexing case, Atlassian documents the JVM parameter -Djira.safeguards.indexing.issue.worklogs=-1 to disable the indexed-worklog limit, followed by a project or full reindex. This can affect issue-search performance. Atlassian recommends testing the change on a test Jira instance first. It is a version-specific Data Center workaround, not a fix for Tempo Cloud’s anonymized authors.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →What currentUser() means in this query
Atlassian describes currentUser() as a function based on the currently logged-in Jira user. Its current Jira Cloud JQL function reference lists supported fields such as Assignee and Reporter in the current-user section, but does not list worklogAuthor. Older Jira documentation and Atlassian examples have used worklogAuthor = currentUser() for native Jira worklogs, so that Cloud reference alone does not establish that every Jira deployment rejects the expression. With Tempo Cloud, the key diagnostic is whether Jira sees the Tempo app account instead of the individual logger. See Atlassian’s Jira Cloud JQL function reference.
Tempo also provides Tempo JQL functions for advanced search, including searches involving Tempo Teams, Accounts, and internal work items. Tempo does not describe these functions as a way to recover an individual author from an anonymized Jira Cloud worklog.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.For integrations, distinguish the app account from the person
If your script needs to find worklogs created by the Tempo app, Tempo recommends filtering on the app user’s accountId rather than its display name. Names can change with platform or branding changes and may be resolved dynamically in historical worklogs; Tempo identifies accountId as the stable Jira-user identifier. This finds Tempo-created worklogs; it does not recover the human logger from an anonymized Cloud record.
Rank #4
![Express Rip Free CD Ripper Software - Extract Audio in Perfect Digital Quality [PC Download]](https://m.media-amazon.com/images/I/41xx28xHa+L._SL160_.jpg)
- Perfect quality CD digital audio extraction (ripping)
- Fastest CD Ripper available
- Extract audio from CDs to wav or Mp3
- Extract many other file formats including wma, m4q, aac, aiff, cda and more
- Extract many other file formats including wma, m4q, aac, aiff, cda and more
Time-zone handling is a separate API consideration, not a cause of an empty author query. Tempo says UI-created worklogs derive startDateTimeUtc from the user’s browser or operating-system time zone at creation, while public API worklogs use the author’s Jira profile time zone. For reliable UTC conversion, Tempo advises using startDate and startTime with the author’s Jira profile time zone rather than treating a UI-created startDateTimeUtc as a stable profile-derived instant. Details are in Tempo’s API guidance.
Quick Recap
Best Value
![MixPad Free Multitrack Recording Studio and Music Mixing Software [Download]](https://m.media-amazon.com/images/I/71ltIxIuz1L._SL160_.jpg)
- Create a mix using audio, music and voice tracks and recordings.
- Customize your tracks with amazing effects and helpful editing tools.
- Use tools like the Beat Maker and Midi Creator.
- Work efficiently by using Bookmarks and tools like Effect Chain, which allow you to apply multiple effects at a time
- Use one of the many other NCH multimedia applications that are integrated with MixPad.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
