To add to this, if a user accidentally changes the status to the trigger status, the approvals that were previously obtained are removed/lost.  This causes confusion.

This is a constant point of confusion for our users.

I believe ASAP is the only constraint that will allow timelines to be auto updated.

You could potentially back into this through the report filtering.   Rather than filtering on status, pull a list of reports that have a project actual completion date > [Date] 12am and project actual start Date < [Date] 12am.

We use the Teams/Agile/Scrum setup for this.  Tasks(stories) are assigned to a team.  Once the team puts the Task(story) into a defined sprint, the Task planned dates on the project are updated to the Sprint Dates.

@BaileyKi - have you confirmed your project settings > Update Type is set to Automatic and On Change?

Completely agree.  Not having multiple conditions limits formatting options.For example, I would want to highly a Planned Completion Date on a project task list if the date if in the past, but only if the task is < 100% (still open).  I cannot do this with the current column rules.

@ChloeWY is correct.  We also tag ourselves when we want to be CC'd on a comment.

Project, Task, and Issue priorities are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.

Project, Task, and Issue conditions are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.