Worklog Check — quick start
Available for Jira Cloud. Ask your Jira administrator to install Worklog Check from Atlassian Marketplace. Free for up to 10 users; larger teams can start a 30-day trial.
After installation, open the app from Jira's Apps menu. Start with Explore fictional demo to understand the report without using project data. For a real review, replace YOURPROJECT in the JQL field with a project you can browse, select start/end dates in YYYY-MM-DD format and choose Analyze visible Jira data.
Set the description, entry-hour and daily-hour thresholds to suit the review. They flag candidates, not violations of a contractual policy. Inspect all linked issue/worklog references before changing any record in Jira.
Example with fictional data
The demo has five entries totalling 25 hours. At an eight-hour entry threshold it shows four candidates, including a matching pair and a 14-hour visible day. The fictional demo uses fixed default thresholds; configurable thresholds apply when analyzing Jira data. The 14-hour group covers DEMO-41 and DEMO-42.
Export
The native Jira app exposes a CSV text area: select and copy its contents into a .csv file. This can include internal information; handle it according to your organization’s rules. Use Edit query and dates to reopen the controls for another review.
Troubleshooting
- Empty: verify project, dates, data and permissions; empty is not proof that another user's data is empty.
- Partial: narrow the JQL scope. Do not treat the result as a complete organization review.
- Permission/unavailable: ask the Jira administrator to check project, issue and worklog visibility and app-access policies.
- Rate limit or API failure: narrow the scope or retry later. The app should not turn an API failure into a clean report.
- License: production requires an active trial/subscription; install from the public Marketplace listing.
For support include the product, approximate time, operation and error text. Remove credentials, bank details and unrelated personal data. Do not send full issue exports unless support has explained why they are necessary.