Your first review
Start with a period whose hours you have already checked. Close Review gives you a fixed starting point to compare with later entries.
Before you start
You need Jira administrator access and access to the selected projects and worklogs. The app is still completing release checks; these instructions describe the implemented workflow.
1. Save the starting point
- Choose your projects and dates.Use a clear period name, such as September close. Choose the timezone used for your review; an entry near midnight can fall on a different date in another timezone.
- Check Jira.Wait for the check to finish. Review the total, coverage and any warnings. A partial check is not a complete starting point.
- Save the starting snapshot.This becomes the fixed comparison for the period. Later checks do not overwrite it.
2. Check again when new value is possible
Run a later check after people have had a chance to add or correct time. Daily monitoring can check eligible periods automatically. The app shows when its latest check finished; an old result is not a live view of Jira.
Checks read Jira over an interval. They are not simultaneous snapshots of every entry. Entries the app cannot read are outside its coverage. A missing entry stays unresolved until its state can be established.
3. Review the difference
Open a change to compare the original and latest duration and dates. Leave a short reason and choose Reviewed, Follow up or No action needed. Follow-ups stay in To review. Save & next helps you move through the list.
If the entry changes again, review its new version. Earlier decisions remain in the history. If another reviewer saved a newer decision, the app asks you to check it before replacing it.
Unfinished notes stay while you move inside the app, but are not saved reviews. Save them before closing or reloading the page.
4. Export a handoff
Open Export review and choose a readable report or a spreadsheet CSV. Check the preview, then download or copy it. If automatic copying is unavailable, use the selected preview text and your browser’s copy command.
The export contains saved decisions, not unfinished notes. A reviewed-only report still shows the outstanding count for the whole period. Store exported files under your organization’s own access and retention rules.
Check that your projects fit
Limits apply to the source inventory, including historical work outside the chosen period. Choosing a short date range does not make a large project smaller.
| Selected projects | Up to 250 total app-visible issues across the selected projects. |
|---|---|
| Worklogs | Normally up to 10,000 source worklogs, within 20,000 examinations across two verification passes. |
| Retained periods | Up to six. |
| Date window | Up to 93 days. |
| Checks | At least 15 minutes between manual checks; up to 12 new scan starts per installation per UTC day, including automatic and failed attempts. |
| History | Up to 2,000 decision and priority-setting events per period. |
| Retention | Period data expires 90 days after the period is created. |
Keep what you need, delete what you do not
Export reviews you need beyond the retention period. You can delete an individual period or erase the app’s data. Treat deletion as permanent. Pausing daily checks stops new automatic checks; it does not extend retention.
An inactive subscription stops new checks, reviews and priority changes. Authorized historical export and erasure remain available within retention. Uninstalling has a separate platform recovery process; reinstalling does not automatically restore your previous reviews. Read the storage and recovery details.