- Home
- Skills
- Workflow Automation
- Jira Rules Builder Skill
Works with the AI Agents you already use
Jira Rules Builder Skill
Build, debug, and optimize Jira Cloud automation rules, smart values, and HTML email templates.
$4.99
Jira Rules Builder Skill
Example session with this skill installed
Create a rule for Jira Cloud that triggers when a 'High' priority task is created. It should look up other open tasks for the reporter and send them a summary email in HTML format.
- Read your context and instructions
- Compiled the jira rules builder
I have designed an automation rule to notify reporters of their existing open tasks whenever they create a new High priority issue. This includes a lookup variable to aggregate related issues and a formatted HTML template.
Jira Automation Rule: Reporter Task Summary
Goal and Assumptions
- Trigger: Issue Created.
- Scope: High Priority tasks.
- Assumption: The 'Reporter' field is populated and has a valid email address.
Proposed Rule Flow
- Trigger: Issue Created.
- Condition: JQL Condition
priority = "High".
Action: Lookup issues using JQL reporter = {{issue.reporter.accountId}} AND statusCategory != Done AND id != {{issue.id}}.
4. Action: Send email to {{issue.reporter.emailAddress}}.
Lookup Variables and Smart Values
lookupOpenTasks: Stores the list of existing open issues for the reporter.{{lookupIssues.size}}: Used to count the number of related issues found.{{#lookupIssues}}: Iterates through the collection to build the list.
HTML Email Template
<div style="font-family: sans-serif; color: #333;">
<h3>New High Priority Task Created: {{issue.key}}</h3>
<p>Hello {{issue.reporter.displayName}},</p>
<p>You have created a high-priority task. We noticed you currently have <strong>{{lookupIssues.size}}</strong> other open tasks:</p>
<ul>
{{#lookupIssues}}
<li><a href="{{url}}">{{key}}</a>: {{summary}} (Status: {{status.name}})</li>
{{/lookupIssues}}
</ul>
<p>Please ensure your workload is balanced before proceeding.</p>
</div>
Validation and Test Cases
- Test 1: Create a Low priority task; verify rule does not trigger.
Test 2: Create a High priority task for a reporter with 0 open tasks; verify email handles the empty list gracefully.
- Test 3: Create a High priority task for a reporter with 3 open tasks; verify all 3 are listed in the HTML body.
Next steps
- Copy the JQL into your Jira search bar to verify the lookup returns the expected issues.
- Replace the placeholder URL in the HTML template with your specific Jira base URL.
- Test the rule in a sandbox project before enabling it globally to avoid notification spam.
Connects securely to your tools. The creator never sees your data.
About this skill
Jira Cloud automation is often fragile and difficult to debug. This skill helps you build, repair, and document complex automation rules, including advanced smart values and lookup variables. It focuses on creating clear rule logic that avoids common pitfalls like execution loops or permission errors.
What it does
- Rule Design builds logic flows with triggers, conditions, branches, and actions.
- Smart Value Resolution identifies correct syntax for dynamic data injection.
- Lookup Variable Planning handles multi-issue data retrieval and empty-result logic.
- HTML Email Templating drafts simple, client-friendly notifications using issue data.
- Error Diagnosis analyzes audit log errors and syntax issues in existing rules.
- Rollout Planning provides test cases and rollback steps for safe deployment.
How it works
- Provide your Jira project context, trigger event, and the desired outcome.
- Share a redacted rule export or audit log error for troubleshooting.
- Review the proposed rule outline, smart value mappings, and configuration snippets.
- Execute the provided test plan in a sandbox or non-production project.
Frameworks & tools
Specifically designed for Jira Cloud Automation (native engine). Handles JSON configuration snippets, HTML/CSS for email templates, and Jira Smart Values syntax.
Why this beats prompting it yourself
Writing Jira smart values and lookup logic by hand often leads to silent failures or execution limit breaches. This skill applies systematic checks for branch scope and variable accessibility that generic models miss. It ensures your HTML templates are email-client safe and your JSON snippets follow standard Jira structures.
Use cases
- Automate notifications based on complex priority and status changes.
- Aggregating data from linked issues into a single summary email.
- Debugging rules that fail due to permission issues or incorrect smart values.
- Creating reusable HTML email templates for service desk updates.
Known limitations
Does not have direct access to your Jira instance. Cannot verify project-specific custom field IDs without an export. JSON snippets are illustrative and may require adjustment for direct import.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
No direct instance access. Requires manual ID mapping for custom fields. JSON snippets are illustrative; direct import compatibility depends on the specific Jira export schema provided by the user.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago