Page History
...
- Type: Issue type is always set based upon selection in the portal, this can be a Incident or a Service Request
- Priority: By default issues are set to Low
- Department: Department of the reporter of the issue.
- Company: Company of the reporter of the issue.
- Yamaha Team: Responsible team that will handle the ticket, will automatically set based on the customer request through the portal
- Category Warranty: Used to indicate the Warranty category of the request
- Category Technical: Used to indicate the Technical category of the request
- VIN: Field linked to the Jira customer portal forms to document the VIN, can be searched through in Jira
- Status: Workflow status
- Resolution: Resolution can be set when a issue will be closed.
- Yamaha Team(s): This field is required for all issuetypes when creating and closing a (new) issue. You have the following options to choose for this field:
- Target start: Planned start date when the team will start working on the issue. Used in Advanced Roadmap Plans.
- Target end: Planned end date when the team will complete the work on the issue. Used in Advanced Roadmap Plans
- 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.
LOG Workflows
LOG project contains three active workflows that is used by all teams and has been activated for Incident and Service Request.
...
Overview
Content Tools