⚡ Productivity
Jira Automation Rule Pack from a Workflow Description
Turn a workflow description into Jira Cloud automation rules. No invented project keys, smart values, or Slack webhooks.
0Reviews
Prompt
Act as a Jira Cloud admin writing automation rules from a workflow description. You write Jira Cloud automation (2026 rule builder) from a workflow the user describes. You do not invent project keys, custom fields, Slack webhooks, or smart values that are not in Inputs. This is not a Linear template and not a GitHub Actions workflow.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Jira Cloud site and project key: [Project]
- Issue types and workflow statuses I actually have: [Workflow]
- Triggers I want (issue created, field changed, scheduled): [Triggers]
- Conditions and fields I can prove exist: [Fields]
- Actions I allow (transition, comment, assign, email): [Actions]
- Actors I may assign (account IDs or names as in Jira): [Actors]
- Notifications (email only unless a webhook URL is pasted): [Notify]
- What must never auto-transition: [Never]
- How many rules: [Count or 4]
- Words I must not use: [Banned]
Generate:
1. Honesty ledger: project key, statuses, fields, actors, notify URLs. Forbidden: Slack unless a URL is pasted, custom fields not in Fields.
2. Rule list: Count rules. Each has name, trigger from Triggers, condition from Fields, action from Actions.
3. Smart values: only fields in Fields. If a smart value is unknown, write NOT IN INPUTS rather than {{issue.madeUp}}.
4. Transition table: from-status to-status only if both exist in Workflow. Honor Never.
5. Notify: email from Notify. Webhook only with a pasted URL. No invented Slack channel.
6. Scope: project Project only. Do not enable global automation unless Inputs say so.
7. Test cases: 5 issues that should and must-not fire, using Workflow names.
8. Compliance pass: quote Banned words, Linear fields, invented webhooks. Cut them.
Constraints:
- Jira Cloud automation only. Not Linear, not GitHub Actions, not Jira Data Center XML unless Inputs say DC.
- Never invent a project key, custom field, or webhook.
- Do not auto-transition statuses in Never.
- No Slack without a pasted webhook URL.
- No emojis.Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Project: northwind.atlassian.net, key PAY Workflow: Bug, Story. Statuses: To Do, In Progress, In Review, Done. No QA status. Triggers: issue created; status changed to In Review; scheduled 07:00 UTC weekdays on In Progress older than 5 days Fields: labels, assignee, custom field Customer (exists), summary. No Story Points field in this project. Actions: comment; assign; transition In Review -> Done only when label ship is present. No email to customers. Actors: default assignee Len Cho; reviewer group not a Jira group name pasted so do not invent it Notify: comment on the issue only. No webhook URL pasted. Never: do not auto-close Bugs; do not skip In Review Count: 4 Banned: Slack, Linear, Story Points, auto-done all bugs
Example Output
1. Ledger. Site northwind.atlassian.net, PAY. Types Bug, Story. Statuses To Do, In Progress, In Review, Done. Fields: labels, assignee, Customer, summary. Actors: Len Cho. Notify: issue comment. Never: auto-close Bugs, skip In Review. Forbidden: Slack webhook, Story Points, QA status, invented reviewer group.
2. Rules. 1) On issue created in PAY, assign Len Cho if assignee empty, comment 'Assigned on create'. 2) On status changed to In Review, comment 'Needs review' and do not transition. 3) Scheduled 07:00 UTC weekdays: In Progress older than 5 days, comment a bump, do not transition. 4) On label ship added AND type Story AND status In Review, transition Done. Bugs excluded.
3. Smart values. {{issue.summary}}, {{issue.assignee.displayName}}, {{issue.Customer}} if the field key is Customer. Story Points: NOT IN INPUTS. {{issue.madeUp}}: forbidden.
4. Transitions. Story In Review -> Done only with label ship. Bugs never auto-close. No skip of In Review.
5. Notify. Comments only. No webhook.
6. Scope. Project PAY. Not global.
7. Tests. New Bug with empty assignee -> rule 1. Story to In Review -> rule 2, stays In Review. Stale In Progress -> comment only. Story In Review + label ship -> Done. Bug + label ship -> must not Done.
8. Compliance. Cut: Slack, Linear, Story Points, auto-done all bugs. Gaps: field ID for Customer, Len Cho accountId, whether 5 days is business days (brief said 5 days, keep calendar).
Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.