Support
Agent-Ready Check for Jira is a Jira Cloud app from Arch Badger 500, LLC. This page explains how to get help.
How to get help
Email support@archbadger500.com.
Please include:
- Your Jira site URL, for example
yourcompany.atlassian.net - The app version. A Jira admin can find it under Apps → Manage your apps.
- The work item key, and for validator problems, the workflow and transition
- The steps to reproduce the problem, and what you expected to happen
- Screenshots or error messages
Never send API tokens, passwords, or other secrets. We will never ask for them.
You can also contact Atlassian Support. Atlassian passes app issues on to us.
How to set up and use the app: see the documentation.
Support hours and response targets
We answer support email Monday to Friday, 9:00 AM to 5:00 PM US Central Time, excluding US federal holidays.
| Severity | Example | First response |
|---|---|---|
| Critical | The app is down for everyone, the validator blocks work items that pass or carry the override label, or there is a security issue | Within 24 hours, Monday to Friday |
| High | A main feature is broken or scores are clearly wrong | Within 2 business days |
| Medium | A feature works only partly, or there is a workaround | Within 3 business days |
| Low | A question, a cosmetic issue, or a feature request | Within 5 business days |
The full terms are in our Service Level Agreement.
If the validator is blocking work you need to move, you don't have to wait for us. Add the override label (by default agent-ready-override) to the work item, or have a Jira admin remove the validator from the transition. Then tell us what happened.
Report a bug or request a feature
Email support@archbadger500.com. Put "Bug" or "Feature request" in the subject line.
A public tracker is coming later. Until then, email is the only channel, and we reply to every request.
Security issues
Email support@archbadger500.com with SECURITY in the subject line. Security reports are handled as Critical.
Please describe the issue and how to reproduce it. Don't include real customer data or secrets.
FAQ
What permissions does the app ask for?
When a Jira admin installs Agent-Ready Check, Atlassian asks them to approve these permissions:
- Read Jira work items (
read:jira-work), to score them - Write work item properties (
write:issue.property:jira), only to save the app's ownab500.ready.v1readiness summary on a work item. This permission cannot edit fields, descriptions, labels or status. - App storage (
storage:app), for project settings
The app asks for no permission to call servers outside Atlassian.
Does the app change my work items?
It never changes fields, descriptions, labels, comments or status, and it never creates, moves or deletes work items. It only saves its own small readiness summary (ab500.ready.v1) on the work items it scores, so you can search scores with JQL.
Does the app use AI?
No. The score comes from fixed rules in the app's code. The app sends nothing to an AI model. It offers optional Rovo tools, which use Atlassian's Rovo.
Where is my data stored? Does anything leave Atlassian?
Agent-Ready Check is built on Atlassian Forge and runs entirely on Atlassian's cloud. Settings are kept in Forge storage, in your site's data residency location. The readiness summary is kept on the work item in your Jira site. We run no servers of our own, and the app makes no calls outside Atlassian.
The summary holds the score, verdict, threshold, failed check IDs, blocker count, override flag, rules version and times. It holds no work item text, no repository names, and no names or account IDs.
The one exception is optional: a site admin can let outside AI tools use the app's read-only Rovo tools through Atlassian's MCP service. This is off unless an admin turns it on. The details are in section 6 of our Privacy Policy.
Why does a score say "rules changed"?
A project admin changed the project's settings after the work item was scored. The app re-scores the work item when someone opens it or edits it, and a background job re-scores the project's scored work items 20 at a time. The panel and the validator always use the current settings.
What happens if the app has a problem during a transition?
The validator lets the transition through. It does this on an app error, if scoring takes longer than 10 seconds, or if it can't read the work item. The panel then shows "Score unavailable" with a way to try again.
How does licensing work?
Agent-Ready Check is sold through the Atlassian Marketplace. Pricing, and any free trial or free tier, are shown on the app's Marketplace listing. Atlassian handles billing and licenses.
If a site's license isn't active, the panel, settings page and Rovo tools ask you to have a Jira admin activate it, the badge says "Unlicensed", and the validator lets transitions through.
How do I uninstall the app, and what happens to my data?
A Jira admin can uninstall it from Apps → Manage your apps. Remove the validator from your workflows first.
When the app is uninstalled, Atlassian's Forge platform deletes the app's settings for your site. Atlassian keeps a deleted copy for 28 days. A reinstall starts with the default settings. If you reinstall and want your old settings back, email us within 21 days of the uninstall and we will ask Atlassian to restore them.
The ab500.ready.v1 summaries are saved in Jira itself, so they stay on work items after an uninstall. A Jira admin can remove them with Jira's REST API: DELETE /rest/api/3/issue/{issueKey}/properties/ab500.ready.v1. See section 7 of our Privacy Policy.