Page History

...

Note
The button should NOT be used for creation of a SD issue.

Software Delivery BUG/Incident issue creation via

...

SD 

Anchor
Software Delivery BUG Software Delivery BUG

If a bugfix is required to deliver a functional/technical solution for the original SD issue a linked Bug and for B2C Incident can be created in the Software delivery project.

...

• 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  SD Classification need to be on 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
• Pending linked ticket execution
• Change Advisoryboard (CAB) 
• Awaiting Development
• 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. Awaiting 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 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  approvalUsed by Infra to request IT management approval for J-sox changes.  How-to create an Infra J-SOX CHANGE issue

...

• SOX CHANGE issue

Statuses SD Default Workflow detailed explanation

...

1. Awaiting Supplier status can be triggered via the Awaiting Supplier  button .
   
   When selecting this option a pop up frame will be opened:
   
   
   
2. Check Comment selection (see marked in red in the above screenshot).
   Default for comment is set to Internal comment. The Internal comment option can be used for only triggering a status update to Awaiting Supplier 
   Use comment: Respond to customer if your message should be shared with the the reporter and requested participants.  
   1. Optional: Add comment to the comment section.  
      
3.  Select the Awaiting supplier response button.
4. After reply from the Awaiting supplier response button is pressed the comment will be added to the ticket and status will be changed to Awaiting Supplier. Description area is optional.
   
   
5. Response from supplier received:
   
   1. Via issue: Status will automatically changed back to status In Progress.
   2. Manually: Select status In Progress.
      

SD:

...

Software Authorization Workflow

The Software Authorization Workflow is triggered for Elevated User right requests: 
The process is explained on the following pages:

• How-to request Elevated User rights - SQL cluster access
• How-to request Elevated User rights - YMPACT YMXXITS1 access

SD: Access Request Onboarding Workflow

...

Training material for this onboarding Onboarding Workflow can be found on the following page:   Jira training for (SD) - Onboarding.

Image Added

SD: Simple 3 step workflow

Workflow used for Issue Type Task and Sub-Task.
Task creation is only used by automatic procedures for Onboarding: Jira training for (SD) - Onboarding.
Sub-Task creation explanation can be found under Jira training Basics - Subtask creation

Statuses SD: Simple 3 Step workflow

...