Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation for when a defect create under a certain module will automatically assign to PIC

wayneliew
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2025

(issuetype in ("Bug", "UT Defect", "SIT Defect", "UAT Defect")) AND ("Parent" = ICOMS-1)Registration Defect Automation.png

its not working, please help! which step i did wrong?

2 answers

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2025

Hi @wayneliew -- Welcome to the Atlassian Community!

Short answer: always add the Re-fetch Work Item Data action immediately after the Work Item Created trigger to reload the data.

 

There is a known racetrack timing defect with work item creation such that the rule can start before all data is available to the rule.  This can lead to strange errors or unexpected condition results due to empty fields.  In a recent post, an Atlassian automation team member stated they know about the problem and are actively working on architectural changes to solve it; there was no timeline communicated.

The mitigation for this is to always add the Re-fetch Work Item Data action immediately after this trigger type.  That will slow the rule a bit and reload the data before the steps proceed.  Please add that and retest.

FYI -- This defect also means one should not use the new feature to add conditions directly to the Work Item Created trigger; instead add the re-fetch and then include separate condition checks.

 

Kind regards,
Bill

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2025

Hi @wayneliew 

Welcome to the community.

What is show in the audit log of the rule, what is the error given.

But is this user granted the correct permissions on the project?

wayneliew
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2025

The user is granted correct permission on the project and there is no error given.

no error msg.png

Like John Funk likes this
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2025

Hi @wayneliew 

Welcome to the community.

Is the JQL condition failing or not and what is the scope of your rule (see rule details)?

Is this set to multiple projects or global?

Simplify your JQL as well, to: issuetype in ("Bug", "UT Defect", "SIT Defect", "UAT Defect") AND Parent = ICOMS-1

Like John Funk likes this
wayneliew
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 22, 2025

The automation is set for a particular project only as team managed. Have tried your simplify JQL, its not working also.

Like John Funk likes this
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2025

Hi @wayneliew 

The rule will only set the reporter based on work item created, when the work type is a Bug,, UT Defect, UAT Defect or SIT Defect, if the Parent field is also set on creation

Is this all true on issue creation.

Does the user you specified, have a license, has permission to the project, is in the right project role?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events