Versions Compared

Old Version 28

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 has all standard Jira Software for Kanban template Issue types active. The issuetypeis activatedactive, 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 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.

...

  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 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: the work is completed without deployment needed (Resolution "Done" is set automatically); or 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: the work is completed without deployment needed (Resolution "Done" is set automatically); or 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)Ticket assignment, only option is canceled).

How to add or change a assignee

...

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

...