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 new issues via the Yamaha Motor Europe Logistics Boards.

The image2022-12-6_10-2-12.png button should be used for creation of a LOG issue.


LOG Issue types

YME Logistics has all standard Jira Software for Kanban template Issue types active. The issuetypeis active, 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 used, see list under LOG Issue types.
  • Priority: By default issues are set to Low
  • Yamaha Team(s): This field is available for all issuetypes and it is optionally.  This field determines on which board a ticket is visible. 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 YME Logistics and has been activated for the issuetypes Epic, Task, Story and Sub-task.

Workflow and status 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: 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).

Workflow and status for the Task, Story and Bug

  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).

Workflow and status for the 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: 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

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.

How to remove a assignee

  1. Click on the assignee field
  2. Remove the name and click image2022-10-28_15-35-2.pngto confirm


    image2022-10-28_15-28-4.png

How to assign an ticket to different department/team

  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)

Project shortcuts

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

  1. Confluence - YME Logistics



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









  • No labels