Documentation
ChronoEntry for Jira (Secure Time Tracking)
Team leads and HR in Jira need to log employee hours against issues and produce reports for project billing or compliance. Existing solutions fail with cryptic errors and failed updates, risking silent data loss, and provide no support response when time records disappear.
Overview
Team leads and HR in Jira need to log employee hours against issues and produce reports for project billing or compliance. Existing solutions fail with cryptic errors and failed updates, risking silent data loss, and provide no support response when time records disappear.
Key Features
- A user can log hours against a Jira issue from the issue view; after saving, the report view filtered by that issue, user, and date range shows the entry without a page reload.
- For tenant A, a direct REST request to the report endpoint for tenant B's site ID returns 404, and tenant B's entries never appear in tenant A's CSV export.
- Uninstalling the app deletes all time-entry data stored for that tenant in Forge KV within one hour, and no copy remains in the app's own logs or cache.
- The app exposes an admin endpoint that, given a user account ID, returns that user's time entries in JSON and then deletes them; this endpoint is callable by the tenant admin.
- At day 30, the app appears in the Atlassian Marketplace with a public price and can be installed into a test Jira site.
Getting Started
Install the app into your Jira instance from the Atlassian Marketplace.
Stuck
Ask a person.
If this guide does not answer your question, email us and a human answers. Name the product, what you were doing, and what happened instead. That is genuinely all we need to start.