Versions Compared

Old Version 10

changes.mady.by.user Bianca van der Meer

Saved on

compared with

New Version 11

changes.mady.by.user Bianca van der Meer

Saved on

Key

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

...

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

  • Affected Version/s: field is by default empty, can be filled with affected version/s used for releases.

  • Labels: tags or keywords that can be added to issues to show whether they possess certain characteristics. If a issue is related to BAU (Business As Usual) activities labels BAU is added. 

  • Epic Link: 

  • Sprint: Multi select field to link the issue to a sprint.
  • Solution Group : This field is used to select a single department. Based upon this  field the ticket will appear in the queue of a department.

  • Application-Module:

  • Yamaha Team

    Yamaha Team is a single select drop down field which is required for all issue types used in YIS. 

    This field includes all teams that exist within YME Information Services. When a new team is founded, an entry is added to this field.

    For example, the entries on 01/01/2023:


    Any team board uses this field to filter on, so it's mandatory to fill in at ticket creation, so that the item will show up on the correct team board.

    N.B.: In the past a free text field "Team Yamaha" was used, in which typing errors caused for tickets to get lost. This old field is in the process of being phased out, so you may still see it on certain screens.


  • Story Points: used for issue estimation and tracking progress of work. Story Points field available for issue type Epic, Change request, Task, Story, Bug, Defect, Spike 


  • DOR: DOR is the abbreviation forDefinition of Ready. Scrum teams generally use a Definition of Ready to clarify whether a Jira issue (Product Backlog Item, or PBI) can be taken into sprint. Within Jira, this process has been summarized in a field, "DoR", which allows tracking what an issue needs to become ready for development.

    The generalized DoR steps are:
    1. PBI created
    2. User story defined
    3. Acceptance criteria defined
    4. Refinement & estimation done
    5. Ready for sprint

We    We find that most teams follow similar steps, so should be able to make use of this field.

...

When closing a Story, Bug or Defect, it is mandatory to full the field "DoD projects":


  • Status: Workflow status
  • Resolution: Resolution can be set when a issue will be closed.
  • Fix/version: Mandatory field  used to assign completed developments to a release scheduled to go to production.
    Additionally, on Kanban boards, closed items will disappear from the board once a fix/version is closed, not earlier.






YIS Workflows

This project contains three workflows, with the distinction being made whether an item contains a software release (development workflow) or not (four step workflow).

...