Table of Contents

Introduction

Never worked with Jira before? No problem. Please first read the Jira training Basics page.
In this chapter below the Jira setup for YME Logistics project is explained.

Jira projects

YME Logistics is using the following Jira-project:

Project	Key	Project type and purpose
YME Logistics	LOG	Jira Software Project

YME Logistics (LOG)

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

The button should NOT be used for creation of a SW issue.

LOG Issue types

Logistics has all standard Jira Software for Kanban template Issue types active. The issuetype is activated, bot is not in use for now.

Atlassian > Jira training for YME Logistics (LOG) > image-2024-6-28_20-13-5.png

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 Request
Priority: By default issues are set to Low
Yamaha Team(s): This field is required for all issuetypes when creating and closing a (new) issue. You have the following options to choose for this field:
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 Workflows

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

Atlassian > Jira training for YME Logistics (LOG) > image-2024-6-28_20-34-53.png

Workflow for the Epic

Atlassian > Jira training for YME Logistics (LOG) > image-2024-6-28_20-22-30.png

Workflow for the Task, Story and Bug

Atlassian > Jira training for YME Logistics (LOG) > image-2024-6-28_20-23-57.png

Workflow for the Sub-task

Atlassian > Jira training for YME Logistics (LOG) > image-2024-6-28_20-25-15.png

Statuses

For the Epic:
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: the work is completed without deployment needed (Resolution "Done" is set automatically); or
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)

For the Task, Story and Sub-task:
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: the work is completed without deployment needed (Resolution "Done" is set automatically); or
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)

Ticket assignment

How to add or change a assignee

From all statuses the Assignee field can be used directly in the ticket to re-assign a ticket to yourself or a colleague.
When a ticket is set to status In Progress, de current user is automatically assigned.

Click on the assignee field or directly on the assign to me button.

To select a colleague it is most easy to type first letters.
When you start typing, suggestions will be made of matching users. Select the user to confirm your choice.