Tracer / Scan
Scan a Jira export
Paste a Jira search export and get data-quality findings and a traceability status in seconds.
No credentials. Your export is not stored. Read this before you paste — it states exactly where your data goes.
- Where it is processed
- Not in this browser. What you paste or choose is sent over an encrypted HTTPS connection to the Tracer service and analyzed there.
- What is sent
- The export text, in full, as the body of one request. No account, no password, and no API token are sent with it.
- What is kept
- Nothing from the export. It is read once to produce the findings below, then released when the request ends. Tracer writes it to no database, no file store, and no cache.
- What is recorded
- The request path, the response code, and how long the request took. No file name, issue key, issue text, person, project, or any part of the export reaches logs or analytics — on a failed scan as well as a successful one.
- What reads it
- Deterministic rules, run once. No AI model reads your data, and nothing you paste trains a model.
- Size limit
- An export over 2,000,000 characters is refused with a size message rather than trimmed to fit.
- Clearing results
- Findings exist only in this browser tab. Close or reload the page and they are gone; there is nothing on our side to delete.
What to bring
- Export the Jira search for the project you want to defend.
- Bring one test-results file in JUnit, CTRF, or OTLP form.
- Name one decision the team has to defend: a release review, an audit request, or a customer evidence question.
Get an export from your Jira: open
https://<your-site>.atlassian.net/rest/api/3/search?jql=project=KEY&maxResults=100
in a signed-in browser tab and save the JSON, then paste it below or choose the file.