Context: We're using subtasks for "bugs" when a Story didn't meet its acceptance criteria and I want to be able to move the parent story from "In QA" to "To-Do" when a new subtask is created, and I want that subtask to take info like assignee from the parent.
I feel like I've tried this a million and one ways. Everything I do fails because "There's no parent." I wrote a simple bit of JQL it has to pass to verify that the parent field is not empty. It passes that, then still thinks there's no associated parent to pull data from.
Any help appreciated.
Unfortunately this is a known behavior with Automation and Next Gen projects. Our development team is aware of the problem and will be addressing it soon. You can follow along with the progress here: AUT-1297
Daniel | Atlassian Team
Okay, that looks a bit different than mine, I'm on Cloud too.
Okay, so I think it is because you are using a next-gen project, I just tested it and get the changed the Parent instead of the updated the Parent entry in the history, and the automation rule is not copying the Assignee. Let me get someone from Atlassian to take a look at it.
Though the issue was resolved. It seems like the problem continues to persist. Is there another possible reason for the "Copy from Parent" not working?
- Trigger: Creation of Issue
- Condition: Created Issue equal Subtasks
- Action: Copy Label From Parent
- Click "+" to add subtask in a Parent Issue. (This is where I think the problem is as Subtasks created via this method might have the Parent added only after it is created?)
Success -> Audit Log -> "Can't find issue to copy from labels"
It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...
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