We use Jira Data Center. I am trying to automate the propagation of a change in the system field Fix Version/s of an epic to all the stories, tasks, bugs under that epic and also to the all the subtasks under the stories, tasks, and bugs. I did the following automation but it seems it is triggered only when the field is manually edited, therefore it does propagate from the epic to the stories, but not to the subtasks. The same automation properly propagates from story to subtask if I edit the story's Fix Version/s.
So my question is if it is possible to do the update on 2nd and 3rd level of issues when I update the epic or if someone can see an error in my automation.
Hello @Miguel Rodriguez
The reason subtasks are not getting changed when the Epic is updated is because the Subtasks are related to the Stories. As the rule is written, the Subtasks would be updated only if they were subtasks directly of the Epic.
To get the Subtasks of the Stories to update when the Epic is updated you would need to be able to create a Related Issues/Subtasks branch within the branch you have for Stories. But Automation doesn't support nesting branches currently.
I think you will need to have separate rules where one makes the update to Stories based on a change to the Epic, and another makes updates to Subtasks based on the change to the parent Story.
<EDIT> I take that back. On the Rules Details page do you see a checkbox for "Allow Rule Trigger"? When that is checked, the rule can be triggered by actions taken by an Automation Rule. If you check that box, then when you update the Epic the first run will update the Stories. That update of the Stories will trigger the rule again and update the stories' subtasks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm glad I could help you.
Please consider marking this Answer thread as Accepted to help other users searching for answers find the threads with working solutions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.