Versions Compared

Old Version 4

changes.mady.by.user Bianca van der Meer

Saved on

compared with

New Version 5

changes.mady.by.user Bianca van der Meer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Deployment request: Triggered by Development software projects used by B2B teams for Ympact,Ympulse, Yamcom deployments.

Image Added Onboarding Issue type used for Onboarding new Users

Image Added Task 

Image Added Sub-task



SD Issues overview

SD Specific Fields

SD mandatory fields have been highlighted in Yellow

Image AddedImage Removed

  • Type: Issue type
  • Priority: By default issues are set to Medium

  • Solution group *: Drop down single select list to define which department will be working on the issue.
    Image RemovedImage Added
  • Team Yamaha: Label field, multi select, always starting with team# <team name>  used to determine which team will be working on the issuename>. This field is only automatically field for Special processes like SQL Execution, Robot Job Changes.
    This field has been replaced with Yamaha Team.
  • Yamaha Team*: Mandatory Drop down single select list to define which (agile) team will be working on the issue.

  • Application-Module*:  Mandatory Drop down single select list to indicate the involved Application-Module of the reported request (issue).
  • Department: Department of the reporter of the issue.
  • Company: Company of the reporter of the issue.
  • Epic Link: Linked epic issue if a issue is related to a Project.
  • SD Classification: Drop down single select list, by default for incoming issues it is set to Business as Usual (BAU)
    Image Added
  • Story Points: used to estimate (in a Fibonacci range) the complexity, effort, and risk inherent to the story. Story Points field available for issue type Change request, Task, Story, Bug, Defect, Spike. 
  • Business value:  used to estimate (in a Fibonacci range)
    Image Removed
    the value of that piece of development to the YME business.
  • Sprint: Multi select field to link the issue to a sprint.
  • Ticket groups: Checkbox field used to group stories and bugs under a YPM Programme/Project. 
    Image Added    Status: Workflow status

  • Resolution: Resolution can be set when a issue will be closed.

...

  • Request Type: Customer portal request type
  • Customer status: Status visible in the Customer portal. This does not always corresponds directly with the issue workflow status.
  • Channel: Portal or e-mail request
  • View customer request: link directly to the Customer portal request. This link can be shared if a customer need to access a specific issue.

SD Workflow(s)

Image Added

...


SD Default Workflow

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

Statuses 

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

Image Removed

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

Image Removed

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)
Image Removed

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

Reopened
Image Removed

Image Added

4. Closed 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.


Other statuses:


Awaiting Customer  Used Awaiting Customer  used when more information/response from a customer (Reporter or Requested participant) is required in order to move forward with a issue.
Image Removed

Awaiting Supplier used Used when more information/response from a supplier  is required.
Image Removed

Awaiting Authorization Used to request approval for Ympact authorization.
SD Classification need to be on : User authorization relatedAwaiting Authorization
Image Removed



Onboarding 
Pending linked ticket execution



Change Advisoryboard (CAB)

Awaiting Development
Awaiting Execution
Deployment validation
Ready to Close


...

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.

SD: Software Authorization flow


Image Added

SD: Access Request Onboarding Workflow

Image Added

SD: Simple 3 step workflow

Image Added

Transition issue through workflow


Basic information how to transition a issue through a Workflow can be found in: Jira Training Basics - Workflow

Via status in Progress the following statuses can be triggered:


Awaiting Customer status

The Awaiting Customer status is used when more information/response from a customer (Reporter or Requested participant) is required in order to move forward with a issue.

...

  1. Awaiting Customer status can be triggered via the Workflow- Respond to customer button.
     Respond to customer button .
    Image Added
    When selecting this option a pop up frame will be opened:
    Image Added

  2. Check Comment selection (see marked in red in the above screenshot).
    Default for comment is set to Internal comment. The Internal comment option can be used for only triggering a status update to Awaiting customer. 
    Use comment: Respond to customer if your message should be shared with the the reporter and requested participants.  
    1. Optional: Add comment to the comment section.  
  3.  Select the Respond to customer button.
  4. After using the Respond to customer button is pressed the comment will be added to the ticket and status will be changed to Awaiting customer. Description area is optional.
    Image Added


Awaiting supplier

The Awaiting Supplier status is used when more information/response from a customer (Reporter or Requested participant) is required in order to move forward with a issue.

Please also read page How to use @mentions to tag a reporter or a commenter directly.

  1. Awaiting Customer status can be triggered via the Respond to customer button .
    Image AddedImage Removed
    When selecting this option a pop up frame will be opened:


  2. Check Comment selection (see marked in red in the above screenshot).
    Default for comment is set to Internal comment. The Internal comment option can be used for only triggering a status update to Awaiting customer. 
    Use comment: Respond to customer if your message should be shared with the the reporter and requested participants.  
    1. Optional: Add comment to the comment section.  
  3.  Select the Respond to customer button.
  4. After using the reply from th the Respond to customer button is pressed the comment will be added to the ticket and status will be changed to Awaiting customer. Description area is optional..
    Image Removed
    Image Added
  5. Response from supplier received:
    1. Via issue: Status will automatically changed back to In Progress.
    2. Manually: Select status In Progress.
      Image Added