Page History

...

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 custor portal.
   
   
5. SD-agent adds Manager of the new user as Requested participant
   1. Add in the comment section a canned response and adjust the information between brackets[ ]
   2. Then click on Share with Customer to send the message.
      
      
      
      
6. Manager receives a notification via e-mail.
   For the manager it will look like below in the Customer portal:
   
7. Manager action:
   1. Manager saves and submit form in customer portal
      
      The form will be locked for editing. Printscreen 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 Task 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-TasksImage Modified

Anchor
Sub-Tasks Sub-Tasks

For internal action by IT department(s) a Sub-Task can be created via the original Onboarding ticket. This is automatically done by selecting the appropriate transition.

...

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

After a Subtask transition is triggered in the original Onboarding ticket the status is changed to Onboarding XXXXXXX
This status change is visible in the Customer Portal:
Example:
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 AddedA 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.
Image Removed

All requested Sub-Tasks can be found under Sub-Task section in the original Onboarding ticket

...

Status of Sub-Task can easily being tracked in original original  Onboarding ticket.
If a Sub-Task is completed it will look as follow in the original ticket.

...

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

A Sub-Task ticket 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.
Image Added

Onboarding Ympact - Req. Ympact

...

This option triggers a subtask


All attachments and onboarding form from original ticket are copied to the subtask:

Description:
Please grand the new AS400 user the requested BPCS environment(s) authorization.

Added directly from last comment original Onboarding ticket
Ympact: YMETST to YMETSTNEW1

Task 

Anchor
Task Task

For non-SD agents a Task can be requested, this is visible in the customer portal
Status:                                                     Transition:

...