What can be run on specific user stories in Copado?

Static Code Analysis can be run on specific user stories in Copado because it allows teams to evaluate code quality and adherence to standards within a defined scope. This process is integral to ensuring that individual user stories, which represent specific features or tasks, meet coding standards and best practices before they are merged or deployed. By applying Static Code Analysis to user stories, teams can identify potential issues early in the development workflow, thereby increasing the overall quality and reliability of the code being produced.

In contrast, other activities like Unit tests are generally executed on the entire application or a broader set of changes, rather than focusing solely on individual user stories. Performance tracking often aggregates data across multiple user stories or releases, providing broader insights rather than targeting specific instances. Deployment scripts, while essential for pushing changes to various environments, do not directly analyze or assess the quality of the user stories themselves. Therefore, Static Code Analysis stands out as the appropriate action that can be closely associated with specific user stories in Copado.