01 · EXPORT
Select the Jira automation JSON
Use the administrator export you already have. RuleSignal does not connect to Jira data APIs.
Jira automation audit and export comparison
Compare automation changes before they reach production.
RuleSignal analyzes and compares Jira automation JSON exports for limits, fan-out, unsafe actions, missing guards, loops, and rule changes. Every file stays in the browser tab.
30deterministic checks
0Jira API scopes
0vendor upload endpoints
Localanalysis and comparison
One controlled workflow
From export to reviewable evidence
02 · COMPARE
Explain what changed
Compare a baseline with the current export and separate changed, added, removed, and unchanged rules.
03 · AUDIT
See evidence and remediation
Findings show the affected rule, exported evidence, operational impact, and a concrete next step.
Privacy by architecture
No backend for your automation export.
Browser memory only
The selected source and analysis exist in the current browser tab and are forgotten when it closes or reloads.
No vendor storage
RuleSignal has no vendor database, object storage, third-party analytics collector, remote, or upload endpoint. Three payload-free Forge counters measure completed real workflows.
No AI processing
The app uses deterministic local checks. Customer exports are not sent to an AI model or third-party processor.
Honest boundaries
A preflight, not a runtime oracle.
RuleSignal does not modify Jira, inspect audit logs, validate live permissions, test external services, or certify that a rule is safe. Missing export evidence is reported as not evaluated, never silently treated as a pass.