Versions Compared

Old Version 15

changes.mady.by.user Mustafa Çakır [X]

Saved on

compared with

New Version Current

changes.mady.by.user Bianca van der Meer

Saved on

Key

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

...

YME Logistics (LOG)

Users can create a new issue issues via the Yamaha Motor Europe support portal, via this portal you can go to theYME Service and Warranty portal to submit a request.
Instructions of the portal forms can be found here: YME Service and Warranty Customer Support Portal GuideLogistics Boards.

The image2022-12-6_10-2-12.pngImage Added button should The image2022-12-6_10-2-12.pngImage Removed button should NOT  be used for creation of a SW LOG issue.


LOG Issue types

YME Logistics has all standard Jira Software for Kanban template Issue types active. The issuetypeis activatedactive, bot but is not in use for now.

The relation or also called hierarchy of these standard issue types can be found in the Jira training Basics under Issue types .

LOG Issues overview

LOG specific fields

  • Type: Issue type is always set based upon selection in the portal, this can be a Incident or a Service Requestused, see list under LOG Issue types.
  • Priority: By default issues are set to Low
  • Yamaha Team(s): This field is required available for all issuetypes when creating and closing a (new) issueand it is optionally.  This field determines on which board a ticket is visible. You have the following options to choose for this field:
    Image RemovedImage Added
  • Target start: Planned start date when the team will start working on the issue. Used in Advanced Roadmap Plans.
  • Target end: Planned end date when the team will complete the work on the issue. Used in Advanced Roadmap Plans.

...

LOG project contains three active workflows that is used by all teams YME Logistics and has been activated for Incident and Service Request.

Image Removed

...

for the

...

Image Removed

...

issuetypes Epic, Task, Story and

...

Image Removed

...

Sub-task.

Image Removed

Statuses

...

Image Added

Workflow and status for the Epic

...

Image Added

  1. To do: work has not started (work can always move back to this status);
  2. In progress: a developer builds & unit tests their own work to meet acceptance criteria (work can always move back to this status);
  3. Refinement: this status is used when the work is not clear what it should be delivered;
  4. On Hold: status used if a work is set on hold;
  5. Done:

...

  1. this field is required and the only option is Done;
  2. Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete (a pop-up will allow filling the mandatory field Resolution, only option is Canceled).

...

Workflow and status for the Task, Story and

...

Bug

Image Added

  1. Backlog: when work is created, it will come to this status first. From this status you can move the work to the another statuses. 
  2. To do: work has not started (work can always move back to this status);
  3. In progress: a developer builds & unit tests their own work to meet acceptance criteria (work can always move back to this status);
  4. Review: a peer reviews any code & functionality;
  5. Done:

...

  1. this field is required and the only option is Done;
  2. Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete (a pop-up will allow filling the mandatory field Resolution, only option is canceled)

...

  1. .

Workflow and status for the Sub-task

Image Added

  1. Backlog: when work is created, it will come to this status first. From this status you can move the work to the another statuses. 
  2. To do: work has not started (work can always move back to this status);
  3. In progress: a developer builds & unit tests their own work to meet acceptance criteria (work can always move back to this status);
  4. Review: a peer reviews any code & functionality;
  5. Done: this field is required and the only option is Done;
  6. Canceled: No further work will be done on this issue, it is not required anymore or has become obsolete (a pop-up will allow filling the mandatory field Resolution, only option is canceled).

...

How to add or change a assignee

...

  1. Click on the Yamaha Team(s) field

  2. Select the Yamaha Team which should take further care of the ticket
  3. Remove yourself as assignee (see instructions above)

Comments

How to add a comment

Use the comment screen at the bottom of the ticket.

When clicking on the Add Comment button at the top you directly jump to the comment screen.

Image Removed

...

Share with customer should only be used by P&A Customer support because these message will be visible in the portal for the reporter and requested participants.
Image Removed

How to use @mention

By using @mentions, you can quickly direct conversation in comments to get needed feedback and keep you moving forward.
That way the issue always stays assigned to you and on your radar.

The following users can being mentioned in Jira:

...

  1. )

...

...

Project shortcuts

The following links are available in SW Jira-Project when opening a ticket at the left panel:

  1. Jira training for Service and Warranty 
  2. YME Service and Warranty customer support portal
  3. YME Service and Warranty customer support portal Guide
  4. YME Service User manuals (in User Manuals (Public) Space

...

  1. Confluence - YME Logistics

Image Added


YME Logistics Boards

Instructions how to access  boards can be found under Jira Training Basics - Boards
The following boards are used by YME LOG:


Program, Roadmap/Plans

Program

Roadmap/Plans