Rule Keeper manual upload: step-by-step manual

Use the manual upload when you want a one-off snapshot of your Automation rules without installing anything. Nothing leaves your browser except a compact summary of each rule.

Who can do this

A Jira global administrator. Jira shows the "Export rules" action only to global admins; project admins can export single rules from the rule editor, which also works but covers one rule at a time.

Steps

1. In Jira click the cog icon (top right) → System.
2. In the left sidebar click Automation (called Automation flows on newer sites). The global list of rules opens.
3. Top right, open the Actions menu ("…" or More actions on some sites) and choose Export flows (Export rules on older sites).
4. A confirmation screen says the export covers all rules. Click Next.
5. Jira processes every rule and shows a progress bar ("Completed N of N flows"). Click Done. Your browser downloads a file named automation-rules-YYYYMMDDHHMM.json.
6. Open the file in a plain-text editor (Notepad, TextEdit in plain-text mode, VS Code). Select all (Ctrl+A / Cmd+A) and copy (Ctrl+C / Cmd+C).
7. Back in Jira open cog icon → Apps, then in the left sidebar under Apps click Rule Keeper, and open the Upload tab.
8. Click into the large text box, paste (Ctrl+V / Cmd+V) and click Create snapshot.
9. A green box reports the number of rules stored and, from the second snapshot on, how many were added, removed and modified.
10. Open Inventory, Changes and Lint.

Polish UI labels for the same path: Ustawienia → System → Automatyzacja → Działania → Eksportuj przepływy → Dalej → Gotowe; the app is under Ustawienia → Aplikacje → Rule Keeper, tab Wgraj, button Utwórz snapshot.

The app shows its texts in English or Polish, following the language set in your Atlassian profile.

What is stored

For each rule: id, name, description (first 2000 characters), state, scope (global or project ids), trigger type, component counts, the ordered list of component types, labels, author and actor account ids, created and updated dates, error notification setting, and a short fingerprint of the rule logic. Rule bodies, smart values, JQL and comments are not stored.

Limits

• The browser parses the whole file, then sends at most 450 KB of summaries to the app. That covers roughly 1500 rules. Larger sites: export rules in segments (Jira supports it) and upload each segment as its own snapshot, or use the sync CLI (docs/manuals/sync-cli.md).
• At most 5000 rules per upload.
• The app keeps the 10 most recent snapshots.

Common problems