How to automate ticket creation in Jira

How to Automate Ticket Creation in Jira

Jira Automation is a built-in rule engine that eliminates repetitive issue management tasks. As of April 2026, automation rules are available on Free (100 rule executions/month), Standard ($8.15/user/month, 1,700 executions), and Premium ($16/user/month, 1,000 executions per rule).

Step 1: Access Jira Automation

Navigate to Project Settings > Automation (for project-scoped rules) or Jira Settings > System > Global Automation (for rules that span multiple projects). Click "Create rule."

Step 2: Choose a Trigger

Select the event that starts the rule:

• Issue created — When any issue is created in the project
• Issue transitioned — When an issue moves to a specific status
• Field value changed — When a specific field (priority, assignee, labels) changes
• Scheduled — Run at a defined interval (daily, weekly, cron expression)
• Incoming webhook — External system sends data via HTTP POST
• Manual trigger — User clicks a button on the issue view

Step 3: Add Conditions (Optional)

Conditions filter which events proceed to the action. Examples:

• Issue type equals "Bug"
• Priority is "Critical" or "Blocker"
• Assignee is empty
• Issue matches JQL query (for advanced filtering)

Multiple conditions combine with AND/OR logic.

Step 4: Add the Create Issue Action

Select "Create issue" from the action list. Configure:

• Project — Target project for the new issue
• Issue type — Task, Bug, Story, Epic, or custom type
• Summary — Issue title (supports smart values for dynamic text: {{triggerIssue.summary}})
• Description — Issue body with details from the trigger
• Assignee — Static user or dynamic assignment (trigger issue's reporter, lead, etc.)
• Priority — Inherit from trigger or set a fixed value
• Labels/Components — Categorization fields

Step 5: Link the Issues (Optional)

Add a "Link issues" action after "Create issue" to create a relationship (blocks, is blocked by, relates to) between the trigger issue and the newly created issue.

Step 6: Test and Enable

Click "Run rule" to test with a simulated trigger. Review the audit log to confirm the issue was created correctly. Publish the rule to activate it.

Practical Example: Auto-Create QA Task from Bug Report

1. Trigger: Issue created
2. Condition: Issue type is "Bug" AND priority is "High" or "Critical"
3. Action: Create issue in the QA project with type "Task"
   • Summary: "QA Verification: {{triggerIssue.summary}}"
   • Assignee: QA Team Lead
4. Action: Link issues — new QA task "is related to" the original bug

This ensures every high-priority bug automatically generates a QA verification task.