What is required if you have deployment tasks in more than one user story in the promotion?

When dealing with deployment tasks across multiple user stories in a promotion, having deployment steps ensures a structured and organized approach to executing the necessary tasks. Deployment steps provide a defined sequence of actions that must be taken to move code or configurations from one environment to another. This is particularly important when coordinating across various user stories, as it helps in managing dependencies and ensuring that each step aligns with the overall deployment strategy.

Using deployment steps allows teams to track progress, identify potential issues, and ensure that the deployment adheres to best practices and governance requirements. By defining these steps beforehand, it enables smoother and more efficient deployments, improving the chances of success and reducing the likelihood of errors that could occur when there are multiple user stories involved.

The other options, while relevant in certain scenarios, do not specifically provide the framework necessary for managing multiple deployment tasks effectively. Deployment logs document what has already occurred, manual intervention may be needed to resolve issues, and administrative approval is often a bureaucratic step that may not be relevant in the context of managing the technical aspects of the deployment process across user stories.