Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JQL branch not working when using trigger "Issue deleted"

Hi everyone,

I am dealing with a strange limitation of JIRA automation. Here is the simple rule:



I try to reach the epic issue of a subtask by using a JQL branching. When using this on a "issue created" trigger, all works well. But when, in this case, I use it in a "issue deleted" trigger, here is what I get:

Error searching for related issues. This is most likely because the following issues don't have a related issue of the type you specified. Try narrowing your search to only include issues that contain links to related issues:

IPUFRA-220: "((key = IPUFRA-96) AND (key != IPUFRA-220)) AND (project in (10034))" - An issue with key 'IPUFRA-220' does not exist for field 'key'.

The JQL is not working because of the clause (key != IPUFRA-220) which seems to be added automatically. But for this trigger, this will always results in this error! This clause is not necessary. Any workaround with this?


1 answer

1 accepted

0 votes
Answer accepted
Yvan Martin Atlassian Team Nov 08, 2020

Hi Cédric,


Developer from Automation here, currently there is a limitation with our JQL branch that continues to add that issue protection when that issue would have been deleted. This is generally necessary to prevent the current issue being processed twice, but in combination with an issue deleted trigger this check should no longer be called.

I've raised a public improvement here to address this, but it's not currently in our roadmap so there's no ETA on a fix:

Apologies for the inconvenience.


Hello Yvan,

Thank you for the raised improvement. Currently I found a workaround by calling a Automation webhook where I performed the necessary actions.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Automation

Announcing the Jira automation template library!

Hi all,  After many months of work, I am delighted to announce the launch of the Jira Automation Template Library!  The Template Library is a new website dedicated to all things Jira au...

702 views 12 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you