On which objects can one find the Run Static Code Analysis button?

The Run Static Code Analysis button is primarily found on User Story objects. This feature allows developers to evaluate the quality of the code associated with the User Story before it moves through the deployment process. By performing a static code analysis, developers can identify potential issues, enforce coding standards, and ensure that the code adheres to best practices—all of which are essential for maintaining a robust and maintainable codebase.

In the context of Copado, User Stories encapsulate the development work that needs to be performed, including Apex code changes. By focusing on the User Story, the Run Static Code Analysis button promotes a process-oriented approach to code quality, making it easier for teams to manage and track code quality as part of their development lifecycle.

While other options may relate to code and deployment processes, they do not provide the specific interface for triggering static code analysis in the same way that User Stories do. For instance, Org Credentials are related to connecting to Salesforce environments, Apex Class pertains to defined pieces of code but does not have a dedicated button associated with static analysis within the context of Copado, and Deployment Records are typically used for tracking deployment details rather than running code quality checks.