Page History

...

Type: Issue type
Priority: By default issues are set to Medium
Solution group *: Drop down single select list to define which department will be working on the issue.
Team Yamaha: Label field, multi select, always starting with team# <team name>. This field is only automatically filled for Special processes like SQL Execution, Robot Job Changes.
Please do no not use it for team assignment but use replacement use field "Yamaha Team" instead.
Yamaha Team*: Mandatory Drop down single select list to define which (agile) team will be working on the issue.
Application-Module*: Mandatory Drop down single select list to indicate the involved Application-Module of the reported request (issue).
Department: Department of the reporter of the issue.
Company: Company of the reporter of the issue.
Epic Link: Linked epic issue if a issue is related to a Project.
SD Classification: Drop down single select list, by default for incoming issues it is set to Business as Usual (BAU)
Story Points: used to estimate (in a Fibonacci range) the complexity, effort, and risk inherent to the story. Story Points field available for issue type Change request, Task, Story, Bug, Defect, Spike.
Business value: used to estimate (in a Fibonacci range) the value of that piece of development to the YME business.
Sprint: Multi select field to link the issue to a sprint.
Ticket group(s) Multi select field used to group stories and bugs under a YPM Programme/Project
Type of work: Field used to track type of work activated for Issue type: Incident

Technical debt: Efforts spent on improving the codebase, enhancing its structure, refactoring, and optimizing it without adding new functionality.
New Development: Efforts dedicated to developing new features, functionalities, or significant enhancements.
Maintenance: Efforts involved in maintaining the system, which includes activities like routine updates, performance tuning, etcetera.
Bug Fixing: Efforts expended to identify and resolve defects or issues reported in the system.
Division: (YME Division)
Multi select field to indicate the YME Division(s) involved/affected. By default empty, value can be entered via the customer portal form or via edit button.
Field is available for Issue type Incident and Service Request. Based on the value entered in this field stakeholders from the Business Divisions can be contacted by the YME IS teams.
Resolution: Resolution can be set when a issue will be closed.

...

Basic information how to transition a issue through a Workflow can be found in: Jira Training Basics - Workflow

Image RemovedImage Added

SD Default Workflow

Image RemovedImage Added

Statuses SD Default Workflow

...

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 Used by Infra for morning check validations.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

...

Awaiting Customer status can be triggered via the Respond to customer button .
Image RemovedImage Added
When selecting this option a pop up frame will be opened:
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 customer.
Use comment: Respond to customer if your message should be shared with the the reporter and requested participants.
Optional: Add comment to the comment section.
Select the Respond to customer button.
After using the Respond to customer button is pressed the comment will be added to the ticket and status will be changed to Awaiting customer. Description area is optional.
Response from customer received:
Via issue: Status will automatically changed back to status In Progress.
Manually: Select status In Progress.

...

Awaiting Supplier status can be triggered via the Awaiting Supplier button .
Image RemovedImage Added
When selecting this option a pop up frame will be opened:
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.
Optional: Add comment to the comment section.
Select the Awaiting supplier response button.
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.
Response from supplier received:
Via issue: Status will automatically changed back to status In Progress.
Manually: Select status In Progress.