Page History

...

• Type: Issue type used, see list under YIS Issue types
  
  
• Priority: By default issues in YIS are set to priority Medium
  
  
  
• Affected Version/s: field is by default empty, can be filled with affected version/s used for releases.
  
  
• Business value:  used to estimate (in a Fibonacci range) the value of that piece of development to the YME business.
  
  

• 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 label BAU is added. 
  
  

• Epic Link: link to epic issue(s) (large feature).
  
  

• Sprint: Multi select field to link the issue to a sprint.
  
  
  
• Requirement status: The requirement test status by version or test plan, is used by XRAY and applicable for issue type Story and Change request.
  
  
  
• Application-Module: Single select list of applications (products) and modules (programs). 
  
  
• Solution Group : This field is used to select a single department that the Yamaha Team falls under. Based upon this field the ticket will appear in the Dashboard queue/filter of a department (manager).
  When all agile teams are formed this field will be phased out for YIS Jira -project.
  
  
  
  
• 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.

  
  
• Target release date: used to track the intended release date aligned with stakeholders.
  
  
• Ticket groups: Checkbox field used to group stories and bugs under a YPM Programme. 
  
  
  

• Story Points: used to estimate (in a Fibonacci range) the complexity, effort, and risk inherent to the story. Story Points field available for issue type 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
  
  
  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 and for all teams.
  When closing a Story, Bug or Defect, it is mandatory in YIS to fill the field "DoD projects":
  
  
  
  
• Installation instructions: Optional field used by some teams to store details for deployment, for example if configuration is required or run a SQL on production system. 
  

...