Page History

...

•  Correct new YIS boards (template/filter) - AJ
  •  Create kanban board template = HIQ → REVIEW 
  •  Java kanban board needs template + filters → move to template AJ : New board
  •  Java kanban board - remove old board: https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=97&view=planning.nodetail&issueLimit=100 - Check with Valentina & Nils
  •  B2B-apps java kanban needs to be removed - Check with Valentina - AJ
  •  All test boards need to be made standard or removed - investigation Andrzej - confirmed - AJ
  •  Ympact team kanban board → scrum ON HOLD
  •  Logistics team kanban board → scrum ON HOLD
  •  Setup Wolverine scrum for Tania https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=107&view=planning&issueLimit=100 
  •  Setup Daycare scrum for Tania https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=108&view=planning.nodetail&issueLimit=100
•  Location of acceptance criteria → impossible. Let's deactivate acceptance criteria for this reason, and use Description instead.
•  Location of installation instructions → impossible. Let's remove the default text instead.
  •  Installation instructions local context? Does Ympact use this? - AJ (Rob de Vries rob.devries@yamaha-motor.nl)
  •  NEW: Rename "Installation instructions" to "Code/Configuration Details" (From SF) Check with Ympact team, EPAM - AJ
•  Releases:
  
  •  NEW: Can we have a "target release date" field in Jira? (SF team) - AJ
  •  Release numbers in versions = Marcel/AJ
  •  Naming convention versions, in Confluence  Release numbering procedure= Marcel/AJ  Release preparation
  •  Target release date global context? - Marcel
  •  NEW: Make Release preparation easy to find in Confluence
  •  Release documentation condensation in confluence - Marcel
  •  Fix/version use? Limit to release managers? - Marcel
  •  Affected Version'version/s System Field add to screens for YIS?
•  NEW: Add Jira rights for PO & BA to set sprint goal (From SF) - Bianca
  •  YIS PO/SM/Dev access rights draft - AJ
  •  User groups - Bianca
•  Workflow cleanups:
  •  NEW: Defect has Generic Test WF assigned, instead of Generic Bug WF. Correct this? (From Diego email) - AJ
  •  NEW: "Done deployment" resolution is set for status "Done" illogically (From SF) - Bianca
  •  NEW: Spikes: can we please skip statusses in WF? (From SF) - AJ
  •  Move bug & defect to Development flow - needs communication
  •  Move Test issuetypes to Subtask flow - needs communication
  •  Move Epics to Subtask flow - needs communication
  •  Rename Subtask flow to Simpe 4-step flow
  •  Create meaningful Epics flow (Arthur)
•  PMO:
  •  NEW: business value activeren op stories (Arthur) - AJ
  •  NEW: business value activeren op epics (Arthur) - AJ
•  CLEANUP / USABILITY
  •  YIS default screen config clean up
  •  YIS field config clean up
  •  NEW: on closing pop-up, add mandatory fix/version field (from AJ) - AJ
  •  Disappearing comments pop-up
  •  Split error YIS: solution group, Yamaha team
•  Test types/screens investigation = AJ
  •  NEW: Test types clean up?: sub-test execution & test set (AJ)
  •  NEW: Standardise field order on test screens? (AJ)
  •  NEW: Remove fix/version from test screens? (Alexa)
•  YMPACT OMS move for issuetypes bug/defect
•  Worklog permissions
•  B2B bord transparancy = Mohan - AJ
•  Add validation for deploymentapprovers group for status to done deployment= Bianca
•  Workflow had to be changed, resolution must be empty for Bitbucket/ Jenkins pull request else a warning is generated.
  •  Generic Bug Workflow Added status Scheduled for deployment, Added transition To scheduled for Deployment,  condition added empty resolution field.
  •  Generic Development Workflow V2   Transition  To scheduled for Deployment: changed condition to empty resolution instead of adding resolution Scheduled for deployment.
    
    Example warning YIS-614 bug fix
    

...