Page History

...

Story example:

• 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.
  
  
  
• Requirement status: The requirement test status by version or test plan, used by XRAY. Used for issue type Story and Change request.
  Image Added Image Added
  
  
• 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: Select list of applications ( products) and modules (programs) 
  
  

• Yamaha Team
  

  Image Removed

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

  Image Added

  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.

  
  
• Ticket groups: Used to group stories and bugs under a YPM Programme. 
  Image Added
  
  

• 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 Story defined
  3. Acceptance criteria defined
  4. Refinement & estimation done
  5. Ready for sprint
  

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

• 
  Image Modified
  N.B. This is an optional feature. Set the field manually in refinement sessions, in case that makes sense for your team.
  
  
• DoD projects: A Definition of Done (DoD) is a term from the scrum framework, which describes the agreement of what it means when an item is set to "Done" status.

...

• 
  Within YME the intent it to validate these three organization-wide requirements for each ticket, because YME is being audited on these three points. For this reason, it is expected that this field will become mandatory across all YME projects in Jira.
  When closing a Story, Bug or Defect, it is mandatory to full the field "DoD projects":
  Image Modified
  Image Added
  
  
  
• Installation instructions: 
  
  
• 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.

...