jira-rules-builder
Build, patch, and fix Jira Cloud automation JSON files for advanced rules, unique lookup variables, and HTML emails.
skill install https://www.promptspace.in/skills/jira-rules-builderAutomate Jira Like a Pro
Creating complex Jira Cloud automation rules via the standard UI can be limiting and error-prone. The Jira Rules Builder skill empowers developers to programmatically generate, patch, and fix Jira automation JSON files, enabling advanced configurations that are impossible through the web interface alone.
What it does
- Beyond UI Limits: Assign unique names to multiple lookup variables (Jira's UI defaults everything to `lookupIssues`), preventing data overwrites.
- Smart Value Optimization: Corrects common syntax errors in smart values, such as improper prefixes inside iteration blocks.
- Bug Prevention: Automatically fixes known Jira import issues, like the "convertLineBreaks" flag that destroys HTML email layouts or incorrect schema versions for email actions.
- Structure Validation: Ensures the output JSON includes site-specific constants (ARIs, Account IDs) required for a successful import.
Why use this skill?
Prompting a generic AI to write Jira JSON often results in schema version mismatches or invalid triggers. This skill uses a specialized knowledge base of Jira's import/export schema—including specific fixes for Scheduled triggers, Rovo Agent steps, and complex JQL patterns for different project types (Team-managed vs. Classic).
Supported Components
- Triggers: Scheduled digests (CRON/Basic), Issue transitions, and JQL-based events.
- Actions: Lookup Issues, Create Variable, Send Email (HTML supported), and Rovo Agent invocation.
- Cross-Platform: Works with both Next-gen (Team-managed) and Classic Jira project architectures.
Use cases
- Weekly status digest emails grouped by epic
- Fixing exported rules with blank or duplicate lookup variable names
- Building multi-lookup rules the UI won't let you configure
- Rovo agent integration in automation rules
Example
Prompt
Sample output preview is available after purchase.
Known limitations
- Sites must manually provide ARI/Account IDs from an existing export for successful import. - Cannot bypass Jira's internal API limits or project permission restrictions. - HTML emails require manual CSS inlining.