Page History
...
A
Sub-task is an activity that needs to be performed to complete a higher-level issue type. It's always part of another issue type.
At the same level as Story, other Product Backlog Items exist with slightly different meanings:
...
This project contains four workflows, with the distinction being made whether an item contains a software release (development workflow) or not (four step workflow).
Any work that can require a deployment uses the "Development" workflow:
These workflow steps are intended for:
- 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;
- On Hold: Status only used for issues related to YNS, Workstream field is mandatory to be filled;
- 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
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
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 INFRA-AS400 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 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.
...
Epics focus on Product Owners preparing the requirements:
These workflow steps are intended for:
- Epic created: work has not yet started (this specific status allows easy searching for open Epics);
- Define business case: the goal of the epic needs to be made clear - what is the current situation, and why do we need to change this?
Secondly, we can only celebrate the success of an initiative, if we make clear how we will measure success - what is the acceptance criteria? - Assign team: only after the business case and acceptance criteria are clear, it make sense to involve a development team.
- In progress: the development team is working to meet acceptance criteria;
- On Hold: Status only used for issues related to YNS, Workstream field is mandatory to be filled;
- Done: the work is completed with deployments done on underlying items;
- Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete.
...
Overview
Content Tools