Support
Agent Ledger 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 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.
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, data is lost, or there is a security issue | Within 24 hours, Monday to Friday |
| High | A main feature is broken or the figures are 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.
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 Ledger, Atlassian asks them to approve these permissions:
- Read Jira work items: work items and their change history (
read:jira-work) - Read Jira users: to tell app accounts, such as AI coding agents, from people (
read:jira-user) - App storage: to save the app's results and settings (
storage:app) - Read linked development data through Atlassian's Teamwork Graph: work items, pull requests, commits, repositories, and Atlassian users linked to them (
read:graph:issue:jira,read:graph:pull-request:external,read:graph:commit:external,read:graph:repository:external,read:graph:user:atlassian)
The app asks for no permission to call servers outside Atlassian.
Where is my data stored? Does anything leave Atlassian?
Agent Ledger is built on Atlassian Forge and runs entirely on Atlassian's cloud. It saves its data in Forge storage, in your site's data residency location. We run no servers of our own.
The app makes no outbound calls outside Atlassian. It stores metadata, such as work-item keys, statuses, timestamps, labels, and pull-request status. It does not store work-item descriptions, comments, attachments, or source code.
It also stores some personal data about the people on your work items and pull requests:
- Atlassian account IDs and display names of assignees, people who changed a status, and comment authors. It keeps the comment author and date, never the comment text.
- GitHub logins (or the author name Jira shows) of pull-request authors.
It uses these to tell AI coding agents from people. The full list is in section 3 of our Privacy Policy.
The one exception to "Atlassian only" goes the other way. If you choose to set up the optional GitHub webhook, GitHub sends pull-request and push events into the app. The app checks each event's signature against a secret you set, then keeps only metadata: the pull-request title, state, author's GitHub login, branch, and labels, and each commit's first line and trailer lines. Nothing is sent back to GitHub.
How are GitHub pull requests linked to Jira work items?
There are two ways:
- Your existing Jira development integration. If your repositories are already connected to Jira, the app reads the linked pull requests through Atlassian's Teamwork Graph. It does this as the person viewing the page, so people only see pull requests they already have access to.
- The optional GitHub webhook. A Jira admin can turn this on in Agent Ledger settings. The app then links a pull request or commit to a work item when its title, branch name, description, or commit message contains the work-item key, such as
PROJ-123. The webhook only sees events from the day it is set up.
How does licensing work?
Agent Ledger 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 app's pages ask you to have a Jira admin activate it, and the app stops its nightly data sync.
How do I uninstall the app, and what happens to my data?
A Jira admin can uninstall it from Apps → Manage your apps.
When the app is uninstalled, Atlassian's Forge platform marks the app's stored data for your site as deleted, and the app can no longer read it. Atlassian then permanently destroys it at the end of its standard retention period. A reinstall starts as a new installation. If you set up the GitHub webhook, delete it in GitHub too, under your repository's Settings → Webhooks.