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 Division. When a new team is founded, an entry is added to this field.

  For example, the entries on 18/07/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 (team#******), 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 group(s) Multi select field used to group stories and bugs under a YPM Programme/Project or QRP
  
  
  
  

• 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. Issue created
  2. Requirements defined - the use case & acceptance criteria are clear, why we want to do this and how we will test;
  3. Prioritized against other work - the product owner has ranked the items in priority;
  4. Refinement & estimation done - developers understand the item and have added estiamation;
  5. Ready for work - any dependencies are managed and the team can start the development.
  
  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.
  When closing a Story, Bug or Defect, it is recommended to fill the field "DoD projects".
  
  
  
  
• Design Review: Optional field activated on Epic, Story,  Bug, Defect and Spike, Task . Field is set to track Design Review for solution design, technical design, tech review.
  Default is set to 'To be determined'. If value is set to “Yes” or “Completed”  it will show up on the Design Review board. Architects can then deliver input on the design and mark as completed when review is finished.
  
  
• 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. 
  
  
• Type of work:  Field to track type of work activated for Issue type Story, Spike, Bug, Task
  
  Technical debt: Efforts spent on improving the codebase, enhancing its structure, refactoring, and optimizing it without adding new functionality. 
  New Development: Efforts dedicated to developing new features, functionalities, or significant enhancements. 
  Maintenance: Efforts involved in maintaining the system, which includes activities like routine updates, performance tuning, etcetera. 
  Bug Fixing: Efforts expended to identify and resolve defects or issues reported in the system.
  
  
• Status: Workflow status summary.
  
  

• Resolution: Resolution is set automatically when an issue is closed.
  

  Status	Resolution	Description
  Done	Done	The task/configuration has been completed.
  Done Deployment	Done - Deployment	Deployment has been completed.

   

• For Status Canceled a resolution can be selected when the issue is going to be closed

  Status	Resolution	Description
  Canceled	Cannot Reproduce	The problem cannot be replicated or is not clear.
  Canceled	Duplicate	The issue is a duplicate of another issue.
  Canceled	Won't Do	The issue will not be addressed, often used for non-issues or low-priority items, or the business has decided not to implement the requested feature.

• 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.
  
  
• Note: Single text field used for reporting for POs, Trainleads and teams to see at a detailed level in one view what exactly needs to be discussed or informed about a story, task or epic.
  

...