...
- 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 field for Special processes like SQL Execution, Robot Job Changes.
This field 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 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 groups: Checkbox field used to group stories and bugs under a YPM Programme/Project.

- Resolution: Resolution can be set when a issue will be closed.
...
- Awaiting Customer status can be triggered via the Respond to customer button .

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.
Image Added
Awaiting supplier
The Awaiting Supplier status is used when more information/response from a customer (Reporter or Requested participant) is required in order to move forward with a issuea supplier has been contacted either via the issue directly or via other communication canals to purchase/request assistance for products/services.
Please also read page How to use @mentions to tag a reporter or a commenter directly.
- Awaiting CustomerSupplier status can be triggered via the Respond to customer Awaiting Supplier button .

When selecting this option a pop up frame will be opened:
Image Removed
Image Added
- 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.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 Respond to customerAwaiting supplier response button.
- After reply from th the Respond to customer button the Awaiting supplier response button is pressed the comment will be added to the ticket and status will be changed to Awaiting customerSupplier. Description area is optional.
Image Removed
Image Added
- Response from supplier received:
- Via issue: Status will automatically changed back to status In Progress.
- Manually: Select status In Progress.
Image Removed
Image Added