Page History

...

The steps in italics are shown on the deployment board, while "Ready for Deployment" or Done or Canceled is the final state on development boards.

Please note that on 27 Feb 2024 17:00 CET the new workflow for B2C/YIS will go live (update image after go-live):
Image Added

These workflow steps are intended for:

• To do: 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 (this step can be skipped);
• Validation: PO/business validates that the functionality is as required, or provides feedback;
• Done: the work is completed without deployment needed (Resolution "Done" is set automatically); or
• Ready for deployment: the work is done & documented, but deployment to production is still needed;

• On Hold: Status only used for issues related to YNS, Workstream field is mandatory to be filled;
• Blocked: Status only used for Consumer Train reporting;
• Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete (a pop-up will allow filling the mandatory field Resolution); or

• Acceptance: the work going through extensive UAT outside of the sprint (this step can be skipped);
• Scheduled for deployment: deployment date is set (this step can be skipped);
• Done deployment: the solution is available and working on production (fix/version is a mandatory field before moving to this status; Resolution "Done Deployment" is set automatically).
  
  
  For some B2B teams a specific transition has been added to move an Issue from Ready for Deployment to Done Deployment, 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.
    

The steps in italics are shown on the deployment board, while "Ready for Deployment" or Done or Canceled is the final state on development boards.

The following statuses allow sprint closure: Done, Canceled, Ready for Deployment (and Acceptance, Scheduled for Deployment, Done Deployment).

YIS Enable Story Workflow

...