Introduction

This document describes how a robotjob (change) request can be created.

A Robotjob Ticket can be created via the following two options

New Robotjob request out of an existing ticket

  1. Open the ticket in the Yamaha Applications Support Desk


  2. Select Workflow , then select Req Robotjob change
  3. It immediately creates a LINKED (implemented by) new ticket until status In Progress + the reporter + assignee prefilled.


    SD ticket status is updated to Pending linked Ticket Execution



  4. Jump to the Robotjob ticket which can be found under Issue Links - Is implemented by section


  5. Complete the text in the Description area 


  6. Make sure correct Solution group is set: 
    Business Applications (ITS Support) or Logistics Applications

  7. Make sure correct Yamaha Team is set

  8. Select correct Application- Module
    If module cannot be specified for SYS200/YLS this can be left blank

     
     
  9. Press Req. SQL or RobotJob approval


  10. Add a comment if needed, and press Req. SQL or Robotjob approval
    If a Robotjob change has already been applied then Retrospective approval? flag Yes need to be selected. Else this can be left empty. 

  11. The original ticket is updated to status: Awaiting RobotJob approval.
    This invokes an approval request which is similar as an SQL approval, ticket status will be changed to Awaiting manager approval





  12. Approver will see the approval request via filter on dashboard:
    1. The approver should select Approve Robot Job  if approved
      1. If Retrospective approval has been requested the flag will be set:


    2. If not approved, the approver adds a comment to the ticket, selects Workflow and Back in Progress
      Assignee repeats from step 5 or closes the issue with resolution Canceled.
    1. For Normal approval the ticket changes to status Awaiting Execution

      Automatically the following comment is added:


    2. For Retrospective approval the ticket will automatically closed and Step 14 and 15 will be skipped


      Automatically the following comment is added including the approvers name:
  14. Ticket will appear in filter results
    1. For Ympact: on Infra AS400 dashboard: Infra Robotjob Change requests waiting for execution
    2. for YLS/SYS2000 on Project management Logistics dashboard: Logistics Applications Robotjob Change requests waiting for execution


  15.  When done, close the ticket via the Resolve button, select resolution Done- Robotjob changes  and then Resolve
    For Ympact this is done by INFRA AS-400 support for Logistics applications support is is done by the person who has completed the RobotJob Change request.






  16. Automatically the original (source) ticket is updated to status in Progress , via Issue links it is visible that the linked ticket is closed.


New Robotjob ticket via Create button (non-preferred)

  1. Via  Create button, select Issue Type RobotJob Change
    Note: This option is only available for users who are member of licensed group:  YMEUACJiraServiceDeskUsers.
  2. A new screen will be opened where you can enter the ticket details:
    1. Add text to the Summary, Description fields
    2. Select Solution group: Business Applications (ITS Support) or Logistics support
    3. Select Application Module:  

       
       
    4. Select correct Team Yamaha
    5. If available include screenshots/attachments to the ticket
    6. Press Create button
         

  3. The requester will receive a notification per mail with the ticket number or check the Queue for open tickets.
    Open the newly created for Type Robot Job Change ticket 


  4. Allocate the ticket to yourself
    1. Click on the Allocate button
    2. select Assign to me
       

      b. Click on the  Allocate button in the Allocate screen


  5. Click on Start Progress


  6. Complete the text in the Description area. Describe manually the change required for the RobotJob. There is no template text available when creating a ticket manually.
    Below text can be  used to copy-paste it in the description field. 

    ACTION:
    Change, Create, Remove, Hold, Release (choose the correct action) 

    Environment / Distributor (P=Process, N=No change)
    YBE : N YCZ : N YDE : N YES : N YFI : N YFR : N
    YHU : N YIT : N YLU : N YMA : N YME : N YNL : N
    YPL : N YPT : N YSC : N YSK : N YTR : N YUK : N

    JOB NAME:
    What should be the job name, which jobname does it concern?

    PROGRAM to be called:

    DEPENDENCIES:
    Indicate possible dependencies and inform how to mitigate them

    TIMING:
    Select the correct timing (SOD, EOD, EOM, SOM, special runtimes etc)

  7. Press Req. SQL or RobotJob approval


  8. Add a comment if needed, and press Req. SQL or Robotjob approval
    If a Robotjob change has already been applied then Retrospective approval? flag Yes need to be selected. Else this can be left empty. 

  9. The original ticket is updated to status: Awaiting RobotJob approval.
    This invokes an approval request which is similar as an SQL approval, ticket status will be changed to Awaiting manager approval





  10. Approver will see the approval request via filter on dashboard:
    1. The approver should select Approve Robot Job  if approved
      1. If Retrospective approval has been requested the flag will be set:


    2. If not approved, the approver adds a comment to the ticket, selects Workflow and Back in Progress
      Assignee repeats from step 5 or closes the issue with resolution Canceled.


    1. For Normal approval the ticket changes to status Awaiting Execution

      Automatically the following comment is added:


    2. For Retrospective approval the ticket will automatically closed and Step 12 and 13 will be skipped


      Automatically the following comment is added including the approvers name:



  12. Ticket will appear in filter results
    1. For Ympact: on Infra AS400 dashboard: Infra Robotjob Change requests waiting for execution
    2. for YLS/SYS2000 on Project management Logistics dashboard: Logistics Applications Robotjob Change requests waiting for execution


  13.  When done, close the ticket via the Resolve button, select resolution Done- Robotjob changes  and then Resolve
    For Ympact this is done by INFRA AS-400 support for Logistics applications support is is done by the person who has completed the RobotJob Change request.










  • No labels