On metadata deployments, I frequently struggle with Report Folders, Workflow Updates, and other configuration elements that have individual users assigned to them. The struggle is that individual users assigned to these config elements often do not exist in the target org. This results in the entire deployment failing, and many times, manually configuring the report, report folder, etc.

A nice solution to this would be a new section on the Problem analysis screen that allows me to exclude the users from the config element that is being deployed.

It is useful to call these scenarios out, because I need to remind developers and admins that the proper way to set these up is to add a group to the folder, workflow rule, etc, then the people to the group. This is the only method that I have found to prevent these configuration elements from failing my deployments.