Install and set up
Install Calibro Test from the Atlassian Marketplace onto your Jira site. There's no configuration screen to fill in first. The first time anyone opens the app it spends about a minute building its own database on your site, says so on screen, and is ready after that.
What it asks permission for
The install prompt lists these grants, and this is what each one is for:
- Read Jira work
- Stories and their descriptions, so a test can cover one and the drafts have something to read; components and fix versions; the search behind the Coverage tab; and the thumbnail of a screenshot attached as evidence.
- Write Jira work
- Three things and nothing else: the Test coverage field on a story, a Bug created from a failing step, and a screenshot attached to the story a run is for. The app never edits, transitions or deletes an issue.
- Read Jira users
- Names and avatars for the people who own tests and run them. The app stores account ids and asks Jira what to call them.
- App storage
- The app's own database on your site, where tests, folders, steps and runs live. Never as Jira issues, and never off Atlassian.
The app declares no external egress at all. Forge enforces that rather than us promising it, and it is why the app is eligible for Runs on Atlassian. The tests drafted from a story are drafted by Atlassian-hosted Claude inside the same boundary.
The Test coverage field
Installing adds one custom field to your site, Test coverage. It appears a minute or two after the install, and it is read-only: only the app writes it, so it always says what the runs say. It works in JQL, saved filters and board swimlanes whether or not it is on a screen — "Test coverage" = Failing is a valid query the moment the field exists.
To see the value on the issue view, add the field to your project's screens the way you would any other. Settings reports whether Jira has the field yet, and what to do if it stays missing. Test coverage describes what the five values mean.
Where the app appears
There is no admin screen to work through before the first test. Settings holds three things — the suggestions switch, how dates and clocks are written, and the state of the field — and none of them needs touching to start. The first thing to do is write a test.