The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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: https://codebarrel.atlassian.net/browse/AUT-2067
Apologies for the inconvenience.
Cheers.
Hello Yvan,
Thank you for the raised improvement. Currently I found a workaround by calling a Automation webhook where I performed the necessary actions.
Cédric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a similar issue. Could you please provide some detail on the workaround you implemented?
Thank you
- Alessandro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alessandro,
You have to send un web post request like this:
Where the body is defined as
After that, you create another rule to catch the post request, like this:
Where the webhook is defined as:
And then, you can do this:
Hope this helps,
Cédric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.