Jira Automation Rule Not Matching Issue Type Even When Log Shows It

Moshood

 

Hi everyone,

I'm trying to create an automation rule in Jira that automatically clones any newly created "Bug" issue to another project (called QA Bug).

Here's what I've done so far:

• Trigger: Issue Created

• Log Action: ISSUE TYPE - {{issue.issueType.name}} → This correctly logs Bug

• Condition:

  • Field: Issue Type

  • Condition: equals

  • Value: Bug

• Action: Clone the issue to QA Bug project

However, the rule fails at the condition, and the audit log says: The following issues did not match the condition:

The log clearly shows: ISSUE TYPE - Bug.

I’ve also tried:

• Changing the condition to is not one of

• Using is one of instead of equals

Still no luck.

 

Bill Sheboy

Hi @Moshood -- Welcome to the Atlassian Community!

There are at least two causes of that symptom:

1) The Issue Created trigger can fire so quickly that some data may not be stable / available when the rule starts.  The fix for this is to always add the Re-fetch Issue action immediately after that trigger.  This will slow the rule a bit, and reload the data before proceeding.

 

2) What is the scope of your rule, in the details at the top: single-project, multiple-project, or global?

When a rule is multiple-project or global and there are team-managed projects impacted, the different issue types could have the same names but different type ID values, causing conditions and rule actions to fail.

The solution is to specifically test the issue type by name, or by the ID for narrower cases.  For example, rather than using the Field Values condition use the Smart Values condition:

• smart values condition
  • first value: {{issue.issuetype.name}}
  • condition: equals
  • second value: Bug

 

Kind regards,
Bill