...

The component field is having a predefined set of labels one can select from. For the YNS project, it is required to use YNS for each story, tasks or epic, feature, milestone or capability.

Component YNS is automatically added for all YNSEU issues and for YIS where Workstream field is filled
For Initiative Ympulse 1.5 component Y1.5 is automatically added for all child issues in YNSEU and YIS linked to Milestone YNSEU-1243
For Initiative Ympulse 2.0 component Y2.0 is automatically added for all child issues in YNSEU and YIS linked to Milestone YNSEU-1745

Example:  Image Added

Teams

Teams can be selected in YNSEU Jira Project via Yamaha Team(s) (multi select)  and in YIS via Yamaha Team (single select) field.

...

Yamaha Motor Next Stage (YNSEU)

YNSEU Issue Types

YNSEU: Issue Type Scheme contains the following Issue types:

YNSEU issues overview

YNSEU Specific Fields

Image Modified Image Modified

• Component's:  Predefined set of labels, Component YNS  is automatically added upon creation of an YNSEU Issue.
• Decision Type:  Single select list, to indicate the Decision type, is only applicable for issue type Decision
• Application(s):  Multi select field to indicate affected application(s), is only applicable and mandatory for issue type Decision
• Workstream:  Used to distinguish which project  items are linked to and is mandatory to be filled in ANY issue type
• Dependent Workstream: Used to distinguish which project items are linked as 'secondary workstream' and to specify dependencies
• Phase: Used to indicate to which Project Phase this issue belongs to
• Yamaha Team(s):  Yamaha Team is a multi select drop down field which is used to indicate which team is involved for this issue and to have the issue reflected on the teams Dashboard or Board.
  
• YNS Deliverables: Used to indicate to which stage of Deliverable this issue is part of
  
• %Completion: Completion percentage for YNS work.
• Final Decision: Multi line Text field to capture the final decision for issue type Decision. This is mandatory to be filled when closing a Decision.
  
• Target start: Planned start date when a team will start working on the issue. Used in Advanced Roadmap Plans. To be filled by YNS Workstream lead, YNS PMO or PO.
• Target end: Planned end date when a team will complete the work on the issue. Used in Advanced Roadmap Plans. To be filled by YNS Workstream lead, YNS PMO or PO.
• Baseline start date: Read only field. Used to indicate original planned  start date, will be set automatically when for first time target start is set. Not applicable for issue type Decision
• Baseline end date: Read only field. Used to indicate original planned end date, will be set automatically when for first time target end is set. Not applicable for issue type Decision

YNSEU Workflows

The YNSEU project contains 2 workflows.

...

Users (licensed and authorized users) can use the  button anywhere in Jira from the top bar.

When using the create button the correct project and issue-type needs to be chosen and  some other (required) fields as well. Required fields are marked with a red * .
Image Modified

Example: Image Modified

Issues can also being created via the Board or backlog. Detailed instructions can be found in Jira training Basics - Issue Creation.

...

You can pin-point communication to a particular recipient by using the "@" sign. 

Managing your work

There are a couple of ways to get track of your work (or the work a team does). Underneath some options you can leverage from:

...

• Default Dashboard: Personal Issue tracking dashboard 
  • System Dashboard
    Includes the following filters:
    • Introduction with link to Customer portal and Portal user guide
    • All my open assigned issues
    • All my request participant
    • Issues iI'm mentioned in
    • All my open watched Issues
    • Open project tickets
      
      
• Dashboards for YNS Project management
  • YNS Management Dashboard
  • YNS PMO DashboardYNS Deliverables Planned vs Actuals Dashboard

• Dashboards per YNS Workstream (first four to be removed soon - replaced by the common Dashboard)
  • YNS Accounting Dashboard
  • YNS S&L (P&A) Dashboard
  • YNS S&L (Units) Dashboard
  • YNS S&L (WTY) (WTY) Dashboard
  • YNS S/4 Common Dashboard

• YME IS Teams Dashboards 

  • YNS YME IS Teams Common Dashboard

  • YMPULSE 1.5 Dashboard

• YNS-YME Dashboards
  • YNS-YME Decisions Dashboard
  • YNS-YME Progress Dashboard
  • YNS WRICEF Interface Dashboard
  • YNS Test Management Dashboard
  • YNS Dependency (Linked Issues) Dashboard
  • YNS Pollution Check Dashboard - For Pilot Go Live
  • YNS Pollution Check Dashboard (To be used for Full Scope later)

• YME/YMC QA & CRs Dashboard
  • YME/YMC QA & CRs Dashboard

• Other YNS Dashboards
  • YNS Reporting & Analytics Dashboard
  • YNS Internal Accounting BFL Deliverables Dashboard

  • YNS Data Migration Dashboard

  • YNS Internal Control Dashboard

  • YNS Quickshifter/Dragonball Deliverables Dashboard (To be removed soon - covered in YME IS Common Dashboard)

TEAM BOARDS

All YME agile teams work with a YIS Board This can be a Scrum or Kanban Board.
Via Boards>View all Boards and  search on  YIS or Team name the results will be visible to access the Team board.

...