...

Incident:  Reporting a incident or outage. Currently all incoming issues submitted via the Jira Customer portal will have Issue type Incident.

Service Request:  Request for information, this .  (This issue type is currently not used anymore.)

Audit: Used for J-sox change requests and IRY issues registered to deliver evidence for auditors.

...

• 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> mandatory for non-agile teams name>  used to determine which team will be working on the issue.
  This field will be has been replaced with Yamaha Team.
  
• 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 set to Business as Usual (BAU)
  
  
• Status: Workflow status
• Resolution: Resolution can be set when a issue will be closed.

...

• Request Type: Customer portal request type
• Customer status: Status visible in the Customer portal. This does not always corresponds directly with the issue workflow status.
• Channel: Portal or e-mail request
• View customer request: link directly to the Customer portal request. This link can be shared if a customer need to access a specific issue.

SD Workflow(s)

Image Modified

If a (bug) fix for a application is required the Bugfix transition can be used to trigger a issue being created in a Development project.

Statuses

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.

Image Added

The ticket will automatically move to next status Awaiting assignment.

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 Added

Image Added

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)
Image Added

In Progress  When starting to work on a ticket use the Start progress button
Image Added
Image Added

Reopened
Image Added

Closed

Awaiting Customer  used when more information/response from a customer (Reporter or Requested participant) is required in order to move forward with a issue.
Image Added

Awaiting Supplier used when more information/response from a supplier  is required.
Image Added

Awaiting Authorization
Image Added

Onboarding 
Pending linked ticket execution



Change Advisoryboard (CAB)

Awaiting Development
Awaiting Execution
Deployment validation
Ready to Close

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

Transition issue through workflow

Awaiting Customer status

1. Awaiting Customer status can be triggered via the Workflow- Respond to customer 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 customer. 
   Use comment: Respond to customer if your message should be shared with the the reporter and requested participants.  
3.  Optional: Add comment to the comment section.  
   
4.  Select the Respond to customer button.
5. 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..
   Image Modified

Change Advisory Board (CAB)

...