Set up the Keepr timer panel in Jira
What the panel does
The Keepr panel sits in the Jira issue view. From it you can start a Keepr timer against the issue you are already reading, watch it tick, and stop it again — without leaving Jira.
Time tracked this way is ordinary Keepr time: it lands in a workspace, against a project, on a task, and shows up in the tracker, reports and digests exactly as time started from the web app does.
Before you start
Three things are needed: Jira Cloud, a Keepr organization on the Ultimate plan, and a Jira site admin to install the app once for the whole site.
The Ultimate requirement comes from personal API tokens, which are how the panel talks to Keepr on your behalf. Each person connects their own token, so everyone's time is recorded as theirs rather than pooled under one account.
1. Install the app in Jira
A site admin installs the app once, for everyone. Jira lists the two permissions it asks for: app storage, which holds your token and the project mapping, and read access to Jira work, which the panel uses to read the issue summary so entry notes carry more than a bare key.
Updates then arrive on their own, with one exception: an update that changes those permissions is a major version, and Jira holds it until an admin accepts it under Apps → Manage apps. If a feature you were expecting has not appeared, look there first.
2. Connect your Keepr account
Open any issue and find the Keepr panel. The first time, it asks for a personal API token. Create one in Keepr under API tokens, give it the timers and projects scopes, and paste it in. The full token is shown only once, when you create it.
Your token is stored per Jira user as a Forge secret, keyed to your Atlassian account: nobody else on the site can see or use it, and it never reaches the page in your browser. “Disconnect” clears it whenever you want.
A token without the projects scope still starts timers — it just cannot create a Keepr task for the issue, so the time is recorded against the project alone.
3. Point the Jira project at a workspace
Each Jira project tracks into one Keepr workspace, and optionally into one project inside it. The panel asks the first time and shows the choice prefilled afterwards; “Change” reopens it.
The mapping belongs to the Jira project, not to you. Set it once and it applies to everyone on the site who uses the panel on that project, which is what keeps a team's time landing in the same place.
4. Start and stop timers
Press “Start timer”. Keepr finds or creates a task for the issue, matched on the issue key, so starting on the same issue again next week reuses the same task instead of piling up duplicates. The entry note is seeded with the issue key and summary.
The panel and Keepr web drive the same timer. Starting here stops a timer running in the web app, and that tab updates live. Keepr never stops a timer without asking, so when there is a conflict the panel offers “Stop it and start here”.
The usual limits apply unchanged — the same rules described in “How do concurrent timers work?” govern how many timers you can run and what an exclusive workspace does.
If something goes wrong
“That token was rejected” means the token was revoked, has expired, or was mistyped; create a new one and connect again. “The token is missing a scope” means it lacks timers or projects — scopes are fixed at creation, so make a new token rather than editing this one.
“Choose a Keepr workspace for this Jira project first” means the mapping in step 3 has not been set. “Personal API tokens are part of the Ultimate plan” means the organization behind the token is not on Ultimate.
“Another timer is already running” and “You already have the most timers Keepr allows” are the concurrency rules, not errors: stop a timer, or take the panel's offer to stop the other one and start here.