Help
Pricing, and the free version 2
Statuswatch is free for sites with up to 10 Jira users. Larger sites pay per user and month, through Atlassian, at the prices below. Every site starts with Atlassian's free trial, and nothing is ever charged without an admin having subscribed.
Prices
Atlassian charges for every user of the Jira site, not for the people who open the panel; that is how every Marketplace app is priced. The price per user falls as the site grows.
| Users on the site | USD per user and month |
|---|---|
| Up to 10 | Free |
| 11–100 | 0.60 |
| 101–250 | 0.42 |
| 251–1,000 | 0.18 |
| 1,001–2,500 | 0.08 |
| 2,501–5,000 | 0.06 |
| 5,001–7,500 | 0.05 |
| 7,501–15,000 | 0.03 |
| Above 15,000 | 0.02 |
A site with 100 users pays USD 60 a month. The binding figure is always the one Atlassian shows on the Marketplace listing for your site's size; annual billing and Atlassian's own discounts are applied there.
Trial, billing and cancelling
Atlassian runs the trial, the billing and the cancellation; Statuswatch never sees a payment detail. The trial is free and ends on its own if nobody subscribes. A subscription is cancelled where it was started: Apps → Manage apps on the Jira site, by a site admin.
What happens without an active licence
When a trial has ended or a subscription has lapsed, Statuswatch stops measuring and says so, in the same sentence everywhere:
"Statuswatch has no active license on this site, so nothing was measured. A site admin can start or renew the subscription under Apps, Manage apps."
The panel and the project page show it instead of their figures, the Rovo agent answers with it, a Confluence page shows the app's name without a figure, the CSV export is not written, and an Automation step fails with it in the rule's audit log, so that a rule does not go on setting dates nobody is paying attention to. The hourly run stops: alerts are no longer sent, and the report fields are no longer refreshed but keep the figures they hold, with the date they were counted. Statuswatch goes on recording when a Confluence page changes status, because Confluence keeps no history and a gap could never be filled in later; it shows none of it until a licence is active again. Nothing is deleted. The project settings page stays open, because the calendars are your configuration, not ours: you can read them, change them and export them at any time, and they are counted with again the moment a licence is active.
Sites that installed the free version
Statuswatch was free for every site until version 3. Going paid is, in Atlassian's terms, a new major version, and a major version never installs itself: a site that has version 2 keeps version 2 until one of its admins chooses to update and subscribe.
- Version 2 keeps working and stays free on the sites that have it. It is not switched off, it shows no reminders, and it is not limited after the fact.
- It is no longer developed. New features arrive in the current version only. Where Atlassian's platform allows a fix to be delivered to version 2, a fault that makes its figures wrong, or a security problem, is fixed there too; this cannot be promised for every case, because the delivery is Atlassian's.
- Updating keeps your calendars. The configuration record is the same in both versions.
- Sites with up to 10 users lose nothing by updating: the current version is free for them.
Questions about a particular site: support@status-watch.io.