Page History

...

Statuses SD Default Workflow

Workflow statuses no development required

1. 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.

...

4. Closed The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.


5. Reopened Re-open issue.  Issue need to be re-assigned to a assignee and will be transitioned to status In Progress.

Workflow statuses development required (old procedure)

1. 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.

2. 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

3. 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)

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

4. Ready to Close Development has been completed SD ticket can be closed manually to inform the user about the changes mad and moved to production environment.

5. Closed The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

6. Reopened Re-open issue.  Issue need to be re-assigned to a assignee and will be transitioned to status In Progress.

Workflow statuses development required 

Other statuses:

• 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: Yamaha Applications Support Desk (SD)
  
  
• Awaiting Supplier Used when more information/response from a supplier is required.
  Detailed information for this status can be found further below under: Yamaha Applications Support Desk (SD)
  
  
• Awaiting Authorization Used to request approval for Ympact authorization.
  SD Classification need to be on : User authorization related.
  

...

• 
  
• 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

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 SD: Simple 3 Step workflow

• To do: work has not started, issue can be assigned (work can always move back to this status);
• In progress: Issue is in Progress (work can always move back to this status);
• Done: the work is completed, resolution is automatically set to "Done";
• Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete. Resolution is automatically set to "Canceled" a comment Screen will pop up to include information why the issue has been canceled (can be selected from any status). 

If a Issue is already closed and will be moved back to status "To Do" or "In Progress" the resolution will be cleared.

...