Page History

...

• Filling Issue attributes:Ticket is created, automation rules are running at the background to fill issue field values.
• Awaiting assignment Onboarding ticket ready for being picked up by IT Servicedesk; Assign ticket to a SD-Agent
• Assigned (to do)  work has not started, Onboarding issue has been assigned to a SD-Agent
• In Progress Issue is in Progress (work can always move back to this status);
• 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: Jira training for Onboarding
  
• Awaiting Supplier Used when more information/response from a supplier is required.
  Detailed information for this status can be found further below under: Jira training for Onboarding
• Access request Ympact Triggers automatic Sub-Task creation: Access request Ympact
• Access request Yams Triggers automatic Sub-Task creation: Access Request Yams
• Access request TM1/Cognos Triggers Triggers automatic Sub-Task creation: Access request TM1/COGNOS
• Access request Jira/Confluence/Bitbucket Triggers automatic Task creation
• Request Mobile Phone: Triggers automatic Sub-Task creation
• Access Request Facility : Triggers automatic Task creation
• Closed Onboarding of the new employee/user has been completed

...

A Sub-Task  is a internal task which is not visible in the Customer portal. For this reason there is no match with the (customer) request type in the customer portal.

Sub-Task Access request Ympact

Status of Onboarding ticket temporary changes to After ticket is created it will automatically transitions back to

...

• Automatically the Ympact Sub-Task is assigned to the same Assignee as the original Onboarding ticket.
• Text: copy  [Example User NAME, USERID] to [New User  NAME,  USERID] is taken from the last comment of the original onboarding ticket. Other text is pre-set via the automation rule.

Sub-Task Access Request Yams

Status of Onboarding ticket temporary changes to After ticket is created it will automatically transitions back to

...

When ticket is transition via INFRA-SD to Solution Group: Infrastructure, Yamaha Team: INFRA-AS400 team the subtask will be visible in Infra-AS400 Dashboard

Sub-Task Access request TM1/COGNOS

Status of Onboarding ticket temporary changes to After ticket is created it will automatically transitions back to

...

Task Jira/Confluence/Bitbucket

Status of Onboarding ticket temporary changes to Image AddedAfter ticket is created it will automatically transitions back to Image Added

1. Task is created 
   1. Automatically following fields are set:
      1. Solution Group: Infrastructure
      2. Yamaha Team: JIRA-APPS
      3. Sprint: Active Sprint
      4. Story Points: 1
      5. Request type No match 
      6. Assignee: Bianca van der Meer
   2. Description is automatically added
      
      

      Task is not visible in the Customer portal 
      

      
      

2. Jira Admin changes status from "To Do" to  "In Progress"
   
3. Jira Admin executes task as requested in Onboarding form
   
   

4. For AD user: Please inform approved groups to be assigned in AD.
   and leave status to In Progress.
   Servicedesk can assign approved rights and close the ticket.

   For non-AD user: Please create/adjust a Jira internal directory account.
   Add user as requested participant.
   Ticket can be closed after granting access.
   
   

5. Assignee of Original onboarding ticket can see status update in the original ticket.
   
   
6. If all required actions are performed Task can be closed.
   
   1. Assignee select Done to close the ticket
      
   2. No action needed, select Canceled and provide reason for cancelation.
      

Task Facility

Status of Onboarding ticket temporary changes to Image AddedAfter ticket is created it will automatically transitions back to Image Added

1. Task is created 
   1. Automatically Assignee is set,  same assignee of Original Onboarding ticket.
   2. Requested Participants YME Reception and Facility-Jira@yamaha-motor.eu are automatically added
   3. Description is automatically added
      Image RemovedImage Added
      

      Task is also visible in the Customer portal 
      

      Image AddedImage Removed
      
      The following section is for Facility & Reception:
      
      
      

2. Facility/Receptions executes task as requested in Onboarding form
   
   
3. Facility/Reception informs via comment in customer portal what action has been taken: Provided Batch, Keys, Desk
   After adding comment select Add
   
   
   
4. Assignee receives comment notification via e-mail
   
   
5. If all required actions are performed and Facility/Reception has given the confirmation all requested items have been handled over to the employee the Task can be closed.
   
   1. Assignee select Status Done to close the ticket
      
   2. Assignee adds comment for share with customer to confirm to Facility/Reception that task will be closed.

...