Hi! Is there a way to update parent issue of a sub-task via automation? Found similar questions but they seem to be relevant for epic links. I tried this (as described here), but it doesn't work although the rule says it's completed successfully. Tried with id instead of key also, no change.
Thanks for any help!
Hello @Blazej
Welcome to the community.
The issue you referenced is for Jira Cloud, while your post is tagged as Jira Server. Which hosting platform are you using?
Can you show us the details of the Audit Log for your rule, and also all the components of the rule?
Hi, thanks! Indeed that post was for Cloud, I missed that :/ I don't think we are using Cloud. I also checked the Audit as you suggested and after all it contains errors, which is weird because when running the rule a small popup tells me it completes successfully:
The Audit complains that parent field does not exist.
I am pretty sure I got the components right because the email sent contains correct values for issue keys. Do you know if there is any way to achieve what I want with a non-Cloud solution?
Sorry for all the newbie mistakes I only started my adventure with automation today :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suspect it is not possible to change the parent of a sub-task via automation on Jira Server/DC. I found that there is an issue for Jira Server that is similar to the one you found for Jira Cloud.
https://jira.atlassian.com/browse/JRASERVER-68763
So far I have not found any references that show how anybody was able to accomplish changing the parent of a sub-task through automation.
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.