Is there a way for a Parent user story automatically be set to Ready once all Children stories are set to Ready?
If you have admin right, you could set up this function. Please find below article for detail:
Task State Updates Parent Schedule State | CA Agile Central Help
Thanks for this info. I am concerned about changing/Enabling this Overall Admin setting since it seems that all Project Admins will have to Disable it, such as Kanban teams, as necessary. I say that because of this statement in the documentation:
"Project administrators can disable this logic. If enabled, schedulable work item schedule states for that project will no longer be affected by changes to task states and users will need to update their own schedule state for stories. If you are doing Scrum or Timebox based work, then leave this enabled. If you are doing Kanban or Flow based work, then leave this disabled."
Most of our teams are doing Scrum and Timeboxes so it appears to be a good option, but I'm unclear who is not and how badly this may affect them since already set at off.
Will this "turn on" automatically for all projects if I set "Project admins can enable and disable task auto state updates " to Yes? If so, is there a way to identify Kanban teams so I may inform them?
Just to clarify, Kun's answer about the Auto State Updates switch applies only to the behavior of user stories when their child tasks are completed. It also only affects Schedule State, not the Ready flag. Your original question mentions child stories, in which case the behavior is quite different. The short answer is that a user story that is the parent to other stories is a special case and wouldn't generally use the Ready attribute because it isn't moved manually via board-style apps like the Kanban Board app, and the Ready flag still cannot be set automatically.
As to the Auto State Updates switch, it's ON globally by default whether or not you set the "Project Admins Can Enable..." switch. Setting the "Project Admins Can Enable..." switch to ON just allows project admins to turn the Auto State Updates switch off (or back on again).
Incidentally, I don't fully agree with the recommendation in the help docs about Scrum vs Kanban teams. The condition that disabling this switch guards against is unexpected changes to work item states. For example, if someone adds a task (accidentally or intentionally) to a previously Accepted user story without disabling Auto State Updates then the work item can be unexpectedly pulled all the way back to the Defined state. Alternately, let's say that you have an Accepted user story where a task was never completed because it was deemed by the team to be unnecessary. With Auto State Updates enabled (the default), if someone later moves that task to In-Progress or Completed then the user story will be moved back to the In-Progress or Completed schedule state.
I know, this is a long answer but to summarize:
Hope something in all that helps!
Retrieving data ...