Getting started
Last updated: 5 September 2026
OnTask is a personal work clock for Jira Cloud, built on Atlassian Forge. It opens onto the work already assigned to you, ranked by what is actually urgent; you start a clock on one thing; and stopping it writes a native Jira worklog, authored by you. That is the whole product. It has no team view, no manager report and no AI.
It stores what it needs inside your own Atlassian site and makes no network calls outside Atlassian.
How you get it today
OnTask is being listed on the Atlassian Marketplace and is not yet installable from there. Until the listing is approved there is no install button and no price to quote.
If you want to run it in your own Jira site in the meantime, write to hello@soverain.cz. When the listing goes live, this page changes and self-service install becomes possible.
What you need
- Jira Cloud. OnTask is a Forge app and runs only on Jira Cloud. There is no Server or Data Center build.
- A Jira site admin to install it, and to approve the permission scopes at install time.
- Issues assigned to you. OnTask ranks your open, assigned work. With nothing assigned it still runs — see Nothing assigned below.
The app asks for these scopes at install:
| Scope | What it's for |
|---|---|
read:jira-work | Read your assigned issues, their fields, comments (to spot unanswered mentions) and existing worklogs; check that you may log work on an issue |
write:jira-work | Create the worklog you confirm, and the optional issue comment. Only ever from the stop screen, only after you press Log it; nothing writes in the background |
read:jira-user | Your own profile, for the timezone a worklog's start time needs; and whether an account still exists, which drives automatic erasure |
storage:app | Keep the running clock, your session history, preferences and drafts in Forge hosted storage on your site |
report:personal-data | Atlassian's Personal Data Reporting API — required because account IDs are stored. See Data & privacy |
There is no external-egress permission and no remote host in the app's manifest. The app is eligible for Atlassian's Runs on Atlassian badge.
Where OnTask lives in Jira
Two places.
Apps → OnTask in the left sidebar. This is the dashboard: your ranked work, the clock, what you logged today, and Settings.
On every issue, an OnTask panel in the issue view. Start a clock on the issue you are already looking at, pause and stop it, or log time you already spent — without going to the dashboard.
Both surfaces share one clock. Start it on the dashboard and the issue panel shows it running; stop it from the panel and the dashboard's Today list updates.
Your first look
Open Apps → OnTask. The page reads your open, assigned issues from Jira and shows three cards — the three that score highest. Under each one:
- Why this one — score N. Open it and you see the arithmetic: which signals contributed how many points. It is not a summary of the score; it is the score. See How the ranking works.
- Start on this. Starts the clock.
Under the cards, Show me the next three pages through the rest of your queue; Back to the top returns to the first three.
The right-hand column has two lists:
- Waiting on you — issues where someone mentioned you in a comment and you have not replied on the issue since. This is derived from the comment thread, so it is an observation, not an accusation: if you answered in a pull request or in chat, the issue will still be listed.
- Today — What you logged — every session you logged through OnTask today, with a running total.
Nothing assigned to you
If Jira has no open issues assigned to you, the dashboard says so and offers Log time on anything — pick any issue by key or by a fragment of its summary, and log time to it. The issue panel works regardless of assignment.
Start, stop, log
- Start on this (a card) or Start a timer (the issue panel). The clock runs; the page title shows the elapsed time, so you can see it from another tab.
- Pause when you are interrupted. Paused time is not counted. Resume when you are back.
- Stop & log. The stop screen opens with the time filled in — edit it if that's not right — and asks for a one-line summary of what you did.
- Log it. OnTask writes a Jira worklog, as you, for that duration. Your summary goes in as the worklog's comment if the switch is on.
Optionally the same screen can also post your summary as an issue comment. That switch is off by default — comments notify everyone watching the issue — and when it is on, the screen shows who will be notified and previews the comment byte for byte. Nothing is rewritten.
Right after logging, an Undo on the confirmation removes that worklog again. Discard stops the clock without writing anything.
The details — how the clock survives a closed laptop, what "left running" does, the manual entry path, the day-crossing check — are in The clock & worklogs.
Settings
At the bottom of the dashboard, Settings & privacy holds everything OnTask lets you change: whether the comment switch starts on or off, the daily total that triggers a one-time confirm, the six sliders that tune the ranking to how you work, and the buttons that delete your data. A site administrator additionally sees a switch that turns OnTask comments off for the whole site.