Frequently Asked Questions

Yes. Stint works with all Jira Cloud products. It installs from the Atlassian Marketplace and requires a Jira Cloud instance - it does not support Jira Data Center or Server.

Open any Jira issue and find the Stint panel in the right sidebar (or below the description, depending on your layout). Type a duration, pick a date, add an optional description, and submit. The worklog appears immediately in Jira's native worklog tab on the same issue.

Click Start timer in the Stint panel on any issue. The timer runs in the background while you work - you can navigate away or close the tab and it keeps going. When you click Stop, Stint calculates the elapsed time and creates a worklog. Only one timer runs at a time; starting a new one stops the previous one.

Use the Timesheet view - a weekly grid where rows are issues and columns are days. Click any cell, type a duration, and press Enter to create or update the worklog for that issue and day. Find it under Apps → Stint → My Timesheet in Jira's navigation.

Yes, if your Jira permissions allow it. When creating a worklog from the issue panel, expand the Author field to select a different user. Project admins and Jira administrators can log time on behalf of any user.

Yes. When logging from the issue panel, change the date field to any past date. Administrators can set a lookback window (e.g., no entries older than 60 days) under Settings → Logging Rules. By default there is no restriction on how far back you can log.

Auto-tracking watches for Jira issue transitions. When an issue moves between statuses (for example, from In Progress to Code Review), Stint calculates the time spent in that status using your configured working hours and creates a worklog automatically for the issue's assignee. Enable it per project under Settings → Auto-tracking.

All worklogs are written to Jira's native worklog API - the same place Jira's own time tracking stores data. Your time data lives in your Jira instance. App state (timer, preferences, pinned issues) is stored in Forge Storage on Atlassian's infrastructure.

No. Stint runs entirely on Atlassian Forge - Aquarium Apps operates no external servers and has no ability to query your Jira data. Forge apps are isolated to your Jira instance and can only access data through Atlassian's permissioned APIs.

Your worklogs stay in Jira. They are native Jira objects - uninstalling Stint has no effect on them. What gets deleted is app-specific state: timer status, user preferences, pinned issues. That data is removed by Atlassian's Forge platform as part of the uninstall process.

Yes. Go to Settings → Import → From Tempo and follow the wizard. Connect a Tempo API token; Stint reads your Tempo history and writes each entry as a native Jira worklog, preserving the original author, date, duration, and description. The import runs in the background - you can stay on Tempo until you've verified everything is complete, then cancel your subscription.

Submit a week's worklogs for approval from the Team Overview; a manager can approve or reject with comments. Approved and submitted weeks lock against further edits. Approval is currently single-level - multi-level approval chains are not yet supported.

Stint is free for the first 10 people in your Jira instance. Each additional person is $2 per month. All billing is handled by Atlassian Marketplace. Aquarium Apps does not process payments directly.

Refunds are governed by Atlassian's Marketplace refund policy. Contact Atlassian support for billing disputes - Aquarium Apps does not process payments and cannot issue refunds directly.

Go to Settings → GDPR → Export my data inside Stint. This downloads a JSON file containing your timer state, preferences, and pinned issues. Your time data (worklogs) is accessible through Jira directly - use Jira's own worklog export or JQL to retrieve it.

Go to Settings → GDPR → Delete my data inside Stint. This removes all app state associated with your account from Forge Storage. If you also want to delete your Jira worklogs, do that directly in Jira - worklogs are native Jira objects and Stint does not own them.

Check two things: (1) Jira's time tracking feature must be enabled - Jira Settings → Issues → Time Tracking. (2) Individual projects can disable the issue panel - go to Project Settings → Apps and confirm Stint is enabled for that project.

A Jira administrator needs to enable it: Jira Settings → Issues → Time Tracking → Enable Time Tracking. Individual projects may also have time tracking toggled under Project Settings → Features.

Timer state is saved in Forge Storage and persists across page loads. If a timer is not showing, check that you are logged into the same Jira account on the same site - timer state is per-user, per-site.