Settings, data and uninstalling

The Settings tab is site-wide: one set of choices for everyone on the site, readable by anyone and changed only by a Jira admin. There are three of them, and none needs touching to start.

Suggestions

One switch: Draft tests from a story's description and acceptance criteria. On, and every story with nothing linked gets drafts in its Tests panel until somebody adds or dismisses them. Off, and the panel shows only the tests that exist. The drafts are written by Atlassian-hosted Claude through Forge and the story text stays inside Atlassian either way; the switch is for teams that would rather not have a model read their stories at all. Tests drafted from a story describes what it does when on.

Dates and times

How every clock and date in the app is written, for everyone on the site. Time is a 12-hour or 24-hour clock. Date is your Jira language's order, or day-month-year, month-day-year or year-month-day fixed. The default is a 12-hour clock and each viewer's own language order until somebody changes it.

Languages

Calibro Test speaks English, German, Spanish, French and Portuguese (Brazil). There is no setting: each person sees the app in the language their Atlassian account uses, so two people on one site can read the same run in two languages. Any other language falls back to English, and European Portuguese reads the Brazilian catalog first. The Test coverage field's values stay English whatever the language, so "Test coverage" = Failing is the same JQL for everyone. More languages are on the roadmap.

The Test coverage field

Settings reports whether Jira has the field yet. It appears a minute or two after the app is installed; if it stays missing, reinstall the app from Manage apps and it is created again. Once present, add it to your project's screens to see it on the issue view — it works in JQL either way. Test coverage has the five values.

Where the data lives

Tests, folders, steps, runs and drafts are stored by Calibro Test in this site's own Forge database — never as Jira issues, and never off Atlassian. Three things are written into Jira itself, and they are Jira's from then on: the Test coverage field's value on each story, any Bug created from a failing step, and any screenshot attached to a story as evidence. Nothing is sent anywhere else; the app declares no external egress and Forge enforces it.

If the subscription lapses

Everything stays readable: the library, every run, the Coverage tab and the field's last value on every story. Writing tests, recording runs, linking and drafting pause, and a banner says so, until a Jira admin renews the subscription under Manage apps. Nothing is deleted and nothing is held.

Uninstalling