Backlog:work has not started (work can always move back to this status);
In progress:a developer builds & unit tests their own work to meet acceptance criteria (work can always move back to this status);
Review:a peer reviews any code & functionality;
Ready for test:waiting for a QA officer (this step can be skipped);
In test:QA officer is performing integration test & regression test;
Validation:PO/business validates that the functionality is as required, or provides feedback;
Done:the work is completed without deployment needed; or
Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete; or
Ready for deployment: the work is done & documented, but deployment to production is needed;
Scheduled for deployment: deployment date is set; Default transition for all teams: To Done Deployment Image Added
For some B2B teams a specific transition has been added to move an Issue to the next status, these options are only visible for users who can approve deployments and are included in group: YMEUACJiraB2BAppsDeploymentApprovers
Image Added BA Deployment : Used for deployments by Lightbeam team for Cognos, TM1, DWH. This options triggers an automation rule to inform stakeholders of the deployment.
Image Added OMS Normal Deployment: used for Application-Module Ympact only, this option triggers creation of a SD Deployment request for OMS. This needs to be approved a IT manager/team lead and will after approval be set to Yamaha Team INFRA-AS400 for move to Production. Via a B2B deployment Distribution list stakeholders are informed of the deployment.
Image Added OMS Interactive Deployment used for Application-Module Ympact only, this option triggers creation of a SD Deployment request for OMS. This needs to be approved a IT manager/team lead and will after approval be set to Yamaha Team INFRA-AS400 for move to Production. Via a B2B deployment Distribution list stakeholders are informed of the deployment.
Done deployment: the solution is available and working on production.