...
Statuses SD Default Workflow
...
Basic workflow statuses
...
1. Filling user attributes first status for incoming tickets. Background process is running to collect user data and fill other fields automatically. No action should be taken when a ticket has this status.
The ticket will automatically move to next status Awaiting assignment.
...
4. Closed The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
5. Reopened Re-open issue. Issue need to be re-assigned to a assignee and will be transitioned to status In Progress.
Workflow statuses development required (old procedure)
1. Filling user attributes first status for incoming tickets. Background process is running to collect user data and fill other fields automatically. No action should be taken when a ticket has this status.
The ticket will automatically move to next status Awaiting assignment.
2. Awaiting assignment Ticket can be assigned, this need to be done via the Allocate button.
For all other statuses the Assignee field can be used directly to re-assign a ticket to yourself or a colleague (instructions below).
Image Removed
3. Assigned to do Ticket is automatically transferred to this status after using the allocate button. Ticket will appear on to do list of a assignee (Filter number 4 in the dashboard)
4. In Progress When starting to work on a ticket use the Start progress button
Image Removed
4. Ready to Close Development has been completed SD ticket can be closed manually to inform the user about the changes mad and moved to production environment.
5. ClosedThe issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
6. Reopened Re-open issue. Issue need to be re-assigned to a assignee and will be transitioned to status In Progress.
...
Other statuses
...
- Awaiting Customer Used when more information/response from a customer (Reporter or Requested participant) is required in order to move forward with a issue.
Detailed information for this status can be found further below under: Awaiting Customer status
- Awaiting Supplier Used when more information/response from a supplier is required.
Detailed information for this status can be found further below under: Awaiting supplier status
- Awaiting Authorization Used to request B2B manager approval for Ympact user/menu/program and Jira/Confluence YPM authorization.
SD Classification need to be manually set to: User authorization related. After approval/decline the issue will automatically be changed back to In Progress. Manager should leave a comment if approved or not.
- Onboarding Used by Infra-SD to trigger pending linked tickets for Facility to prepare a batch and keys for new employees , this will be replaced by a new procedure: Jira training for (SD) - Onboarding
Workflow statuses development required
- Pending linked ticket execution Temporary status Triggered when a linked ticket is created for Elevated user rights or RobotJob Change request
Instructions for these procedures can be found on the following pages: How-to request Elevated User rights - SQL cluster access , How-to request Elevated User rights - YMPACT YMXXITS1 access , How-to request a Robotjob change
- Change Advisoryboard (CAB) Triggers a CAB issue creation for approval request of fixes and creation of a functional/technical conceptional design document , this will be phased out completely as it will be covered by the Yamaha Portfolio Board and Software project(s).
- Awaiting Development Status set when a linked Sofware Delivery ticket is created, see explanation under Software Delivery BUG/Incident issue creation via SD
- Awaiting Execution Used for SQL Process for SQL execution.
- Deployment validation
- Ready to Close Triggered when a linked Software Delivery issue is closed. see explanation under Software Delivery BUG/Incident issue creation via SD
- Review Approval Used by Infra for Issue type Audit to have J-sox change reviewed. How-to create an Infra J-SOX CHANGE issue
- Awaiting manager approval Used by Infra to request IT management approval for J-sox changes. How-to create an Infra J-SOX CHANGE issue
...