...
LOG project contains three active workflows that is used by all teams and has been activated for Incident and Service Request.
Workflow for the Epic

Workflow for the Task, Story and Bug

Workflow for the Sub-task

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.
The ticket will automatically move to next status Awaiting assignment.
- Awaiting assignment Ticket is ready to be assigned to a team (Yamaha Team) /assignee

- In Progress When starting to work on a ticket use the 'Start progress' button, ticket will automatically be assigned to the current user.

From all statuses you can always go back to status 'In Progress' , use transition 'To In Progress' for this 
From In Progress you can also go back to status 'Awaiting Assignment'. The assignee is then automatically removed. 
- From status In Progress several Awaiting statuses can be set:

Awaiting Customer used when more information/response from a customer (Reporter or Requested participant) is required in order to move forward with a issue.
When a customer responds the ticket will automatically be changed back to status 'In Progress'
Awaiting Warehouse used when more information/response from Warehouse is required. When response is received, change ticket manually back 'To In Progress'.
Awaiting YME Colleagueused when more information/response from YME colleagues from another division/department is required. When response is received, change ticket manually back 'To In Progress'.
Awaiting Supplier/Factory used when more information/response from a supplier or factory is required. When response is received, change ticket manually back 'To In Progress'.
- Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened. P&A customers support will inform the customer and close the ticket.

...