Onboarding Flow

Introduction

Never worked with Jira before? No problem. Please first read the Jira training Basics page.
This chapter is part of is part Jira training for Information Systems, below the Jira setup for Information Systems - Yamaha Applications Support Desk (SD)  Onboarding procedure is explained.
This procedure is used by IT Servicedesk.

All Onboarding requests will be processed via Recruitment and HR.
HR is responsible for creating the actual ticket for the IT Servicedesk.
Portal instructions how to fill the onboarding form Draw IO file can be found on : YPM-105 Onboarding flow Successfactors - ADthe following page: Onboarding process.

Onboarding Flow

Onboarding procedure in Jira

1. Onboarding ticket is created by HR, reporter = HR-Jira@yamaha-motor.eu [YME HR]
2. After creation ticket will be transitioned to status Awaiting assignment
3. SD-agent allocates ticket via button to him/herself
4. SD-agent set issue to  
   After transitioning the Onboarding ticket to status In Progress the Onboarding form will automatically being attached.
   Please make sure you have the Forms tab open to view the form
   
   
   The form is directly visible in the customer portal.
   
   
5. SD-agent adds Manager of the new user as Requested participant
   1. Add in the comment section a canned response "SD_Onboarding NEW" and adjust the information between brackets[ ]
   2. Then click on Share with Customer to send the message.
      Image RemovedImage Added
      Image RemovedImage Added
      
      
      
6. Manager receives a notification via e-mail.
   For the manager it will look like below in the Customer portal:
   Image RemovedImage Added
   
   
7. Manager action:
   1. Manager saves and submit form in customer portal
      
      The form will be locked for editing. Printscreen Print screen from original onboarding ticket
      
   2. Form will be attached as PDF. This PDF file is not visible in the customer portal, only in the original ticket for SD-agents.
      
8. Sub-task and Jira training for Onboarding can be requested according to selection made in the Onboarding Form.
9. After all linked Sub-task and tasks are completed the Onboarding ticket can be closed by the SD-Agent.
   1. Use a canned response: 
      
      

Sub-Tasks

Anchor
Sub-Tasks Sub-Tasks

...

       Status:                                                     Transition:
Image Removed
Image Added

Transitions are visible in the Onboarding ticket via the  (workflow)buttons

...

For non-internal action by divisions/departments other than Information Systems Systems  or for Scrum teams a Task can be created via the original Onboarding ticket. This is automatically done by selecting the appropriate transition.

Status:                                                     Transition:

Image RemovedImage Added

Transitions are visible in the Onboarding ticket via the  (workflow)buttons

Req. Facility
Image Removed

the Workflow menu

Image Added

After a Task After a Subtask transition is triggered in the original Onboarding ticket the status is temporary changed to Onboarding XXXXXXX
Image Removed status Access request XXXXXXX

This status change is visible in the Customer Portal:
Image Added
Image Removed

Image Added

After the Sub- Task creation the original SD ticket automatically transitions back to In Progress.
This status change also reflects in the customer portal:
Example:

Image RemovedImage Added

All requested Tasks can be found under Issue Links section in the original Onboarding ticket

Image Added

Task workflow and procedure

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.

Task Facility

1. Task is created 
   1. Automatically Assignee is set,  same assignee of Original Onboarding ticket.
   2. Description is automatically added
      
      

      Task is also visible in the Customer portal 
      

      
      
      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 Task can be closed.
   
   1. Assignee select Done to close the ticket
      
   2. Assignee adds comment for share with customer to confirm to Facility/Reception that task will be closed.

No action needed, select Canceled and provide reason for cancelation.

Task Jira/Confluence/Bitbucket

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
      Image Added
      

      Task is not visible in the Customer portal 
      Image Added

      
      

2. Jira Admin changes status from "To Do" to  "In Progress"
   Image Added
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
      Image Added
   2. No action needed, select Canceled and provide reason for cancelation.
      Image Added

Onboarding Form

The Onboarding form has been setup in Pro Forma Forms. If it is not working properly please reach out to Bregje Mank, Daan Libeton, Jira administrator.

A open form always needs to be saved and submitted.

...