Versions Compared

Old Version 72

changes.mady.by.user AJ van Spanje [AgileVisor]

Saved on

compared with

New Version 73

changes.mady.by.user Bianca van der Meer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.

    • BA Deployment : Used for deployments by Lightbeam team for Cognos, TM1, DWH. This options triggers an automation rule to inform stakeholders of the deployment.

    • 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 INFRAiSPARKLE-AS400 iSERIES for move to Production. Via a B2B deployment Distribution list stakeholders are informed of the deployment.

    • 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 INFRAiSPARKLE-AS400 iSERIES for move to Production. Via a B2B deployment Distribution list stakeholders are informed of the deployment.

...