Cardinal Ruler: Configuration Change Management for Jira
OVERALL RATINGS
INSTALLS
17
SUPPORT
- Partner Supported
Key highlights of the appA governed deployment pipeline for Jira configuration: packaged, pre-flighted against the target, approved, deployed, retained

Stop retyping changes between Jira sites
The retype cycle disappears. You design the change once on your origin site, and the approved package is what reaches the target site. No runbook to write, nobody transcribing it by hand, nothing to re-test.
Answer the audit question with a file
What changed, who approved it, and why. Each change gets its own folder of plain files in a Git repository your organisation owns, every review round included, so the answer outlives the people who made the change.
See what will change before anything changes
A read-only pre-flight checks the package against the real target site and reports every gap. Each finding has to be decided before the change can pass, and nothing is written to the target until it is approved.
Supporting media
More details
Book a demo | Features | Security | Docs
Cardinal Ruler turns a Jira configuration change into a governed deployment: authored on your origin site, pre-flighted against the real target, approved as a frozen plan, deployed in dependency order, recorded.
Use Cardinal Ruler to:
- Package the configuration and everything it depends on, not a runbook
- See every gap against the target site before anything is written
- Require approval from people who did not design the change
- Deploy only what the approval covered, in dependency order
- Commit what changed, who approved it and why to a Git repository you own
Best for organisations where a Jira configuration change needs review, approval and an audit trail that outlives the people who made it.
Built for regulated organisations by an Atlassian Solution Partner certified to ISO 27001. Runs on Atlassian Forge, so configuration only leaves Atlassian for the Git repository you nominate.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy and security questionnaire has been filled by the partner
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Cardinal Ruler: Configuration Change Management for Jira integrates with your Atlassian app
Version information
Version 3.0.0•for Jira Cloud
- Release date
- Nov 13th 2026
- Summary
- Major version update
- Details
GitHub support: the audit repository can now be on GitHub as well as Bitbucket Cloud. Setup takes the repository URL and has a quick start guide.
More configuration deploys:
- Update workflow schemes already in use: pre-flight maps missing statuses, counts the work items that move, and the deploy checks the migration.
- Move projects to a deployed work type screen scheme or priority scheme.
- Work types, issue link types, work type schemes, permission schemes and notification schemes now deploy. Grants and recipients are added, never removed.
Safer workflow rules: select-list options and custom fields are matched on the target by name and type, not ID. App rules, such as ScriptRunner post-functions, become manual actions instead of being dropped.
Plus stale-page and concurrent-edit protection, and many smaller fixes.
Upgrade: a site administrator must approve this update under Manage apps, as the app can now connect to api.github.com. Bitbucket connections keep working.
- Payment model
- Paid via Atlassian
- License type
- Commercial