Test a control the way an auditor does, on the records already in Jira.
Most teams run their change approvals, access requests and incident reviews in Jira. When an auditor asks whether a control worked all year, someone exports a spreadsheet, picks rows by hand, opens each record, takes screenshots and writes up what they saw. Reperform does that work inside Jira, shows its reasoning for every record, and leaves the judgement to named people.
Five controls come ready-made: changes approved before implementation (one for a service desk, one for a workflow of your own), emergency changes approved after the fact, access approved before it is granted, and major incidents followed by a review. Adapt one to what your site calls things, and it becomes a control of your own.
Reperform finds every record that should have been subject to the control in the period and says how it searched, so a reviewer can run the same search.
It plans the sample size from how often the control operated in the period and draws the sample from a seed. Anyone who has the seed draws the same records. A sample is drawn once; testing more items extends it in the order the seed already fixed, so nobody can keep the sample they like best. Every sample stays on the site's register, even when its test is deleted, with who deleted it, when and why.
Each attribute of the control is tested against each sampled record, from the record's own history: who approved and when, who started the work and when, whether the same person did both. Every result is Pass, Exception, Needs a person or Not applicable, and comes with the evidence it rests on.
Where the record cannot settle a question, a person does, in their own name and with a note. A person can also overrule a result, and the workpaper shows the automatic result beside the person's.
The preparer concludes. A second person reviews and signs. Reopening a test is recorded with its reason.
Everything a reviewer needs to reperform the test is written to a Confluence page: the control, the search, the sample and its seed, every other sample drawn for the same control and period, each result with its evidence, every decision, the conclusion and the signatures.
Try it on the built-in sample data first: 51 change requests with 12 problems planted in them for you to find, and one question that only a person can answer.
Reperform adds an assistant to Rovo. It answers questions about your tests, checks one record against a control before an auditor does, and runs the mechanical steps of a test when you ask: start it, read the population, draw the sample.
It cannot decide a result, conclude a test or sign one. It has no tool for any of these, on purpose. Asked to, it says who does it and where.
The same tools are available to agents you build yourself and, if your administrator allows it, to other AI clients through Atlassian's MCP server.
Jira Cloud. Four of the ready-made controls are written for Jira Service Management; the editor fits a control to any workflow.
Confluence, if you want workpapers written as pages. Without it the workpaper is available as text.
Rovo, for the assistant.
Reperform runs entirely on Atlassian's Forge platform. It has no server of its own, sends nothing outside Atlassian, and keeps no person's name: it stores account IDs and asks Jira for the current name whenever it shows one.
As installed, everyone who can use Jira on your site. A Jira administrator can limit Reperform to administrators and the members of chosen groups, on the page "Reperform access" in Jira's admin settings. The limit holds on every screen, for the assistant, and for AI clients connected through MCP.
Install Reperform on your Jira site
The link opens Atlassian's install page for the app. Press Get app, choose your site, tick Confluence if you want workpapers written as pages, and press Install. You need to be an administrator of the site.
Write to truesquarelabs@gmail.com.
Reperform is made by TrueSquare Labs. It was designed and built by Claude, an AI model made by Anthropic.