Forums

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

Work Item Created Clear Fields does not respect condition

jessica_huebner
Contributor
August 18, 2025

As a Jira administrator, I want to implement an automation in my project that clears certain fields when a work item is created when a linked work item with 'Clones' relationship is present. The automation rule does not seem to respect the Linked work items present Types: clones that I've set. 

Context: Since there is no When" Work item is cloned, I am using the When: work item created, with a Linked work items present Types: clones as a condition (see attached screenshot). When I create an issue, the automation clears some fields unexpectedly even though there's a linked Clones work item.

How can I adjust this to work as expected? Your help is appreciated!Clone issue condition.png

2 answers

1 accepted

0 votes
Answer accepted
Bert Dombrecht
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.
August 18, 2025

Hi @jessica_huebner ,

Can explain the unexpected behavior in more detail?
Or share the audit log of the unexpected automation triggers?

I have checked my test project configuration to rule out any potential interference:

  • Project default assignee
  • Component default assignee
  • Workflow post-functions

I have set up an automation that clears the assignee field if an (assigned) work item gets cloned, like you've shown in your screenshot.

-> I've also added a log entry to each step, to enrich the audit log.

This seems to work as expected:

  1. Just create an assigned work item: the assignee is kept, the automation rule audit log says "No actions performed".
  2. Clone an unassigned work item: the work item is cloned, the automation rule audit log says "No actions performed".
  3. Clone an assigned work item: the work item is cloned and the assignee is removed.
  4. Clone an unassigned work item and assign it in the clone pop-up: the work item is cloned and the assignee is removed.
  5. Create an assigned work item and set the clone link in the create screen: the work item is created and the assignee is removed.
jessica_huebner
Contributor
August 18, 2025

Thanks @Bert Dombrecht

I think this may have been user error. I just re-tested this after checking everything (didn't make any changes) and it seems to be working as expected. When I checked my audit log, It does say 'No Actions Performed', which is what I expected to happen.

Thanks for much for your insight! Great call to check the automation audit log! :)

0 votes
Shawn Doyle - ReleaseTEAM
Community Champion
August 18, 2025

Hi @jessica_huebner 

If I understand this correctly, the automation is working even if it is not a clone?

jessica_huebner
Contributor
August 18, 2025

Suggest an answer

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

Atlassian Community Events