Page History

...

1. Edit Yamaha Team field configuration, Add all issue types and all IT project but YPM Project, Programme

2. Add Yamaha Team field to all screens where Team Yamaha is used.

3. Bulk updates per team to fill Yamaha team field, same as Team Yamaha. If there are more then 2 removed from selection. 

4. Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty. Fill Yamaha team field if we know team.

5. Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty, inform team leads to set Yamaha team field.

6. Connect Yamaha team field in Big Picture for YIS resource planning scrum teams. 

7. Add team members scrum teams (Bianca/René, help of AJ?)

8. Check workflows/automation rules for Team Yamaha/Yamaha team CAB/YPM

9. Set Yamaha team field required in YIS configuration scheme
10. Set Yamaha team field required for other Dev, CAB scheme as well.
11. Remove team Yamaha from screen in YIS.

RENE REQUIRED

•  Scrum & Kanban template
  •  Marvels epic needs to be removed → Show Rene first
  •  Marvels old scrum needs to be removed → Show Rene first
•  Resolution stop using, set per project/workflow 
  •  Create list per project/workflow = Bianca
  •  Review list per project/workflow = Rene
  •  SD resolution list = Rene, also to be discussed with BAU team/ SD Infra
•  Remove/change resolutions from reporting
•  Reporting request from Vladislav addon 

  Jira
  server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key SD-35530

  = Rene/AJ/Bianca/Revathi
•  Jira admin changes communication = review
•  DoD required / UAT / on epic? = Rene/Nils/ AJ
  DOD project = team
  DOD = Admin
  René: DOD not via Confluence page but directly in Jira, to be further discussed
•  EPIC used for operational support, deployments, user authorization, Jira activities,  J-sox, gdpr, sql approval, job change request, replace by SD classification list = Bianca
  •  List epics
    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YIS-441

    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YIS-438

    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YM-686

    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YIS-451

    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YIS-449

    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YIS-455

    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YM-705

    •  

      Jira
      server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key YIS-437

  •  Change to custom field, single select SD classification = Bianca
    •  Start with new tickets
    •  Automation rules; create, copy from etc.
    •  Workflows
    •  Filters
    •  Dashboards
    •  Boards
    •  Bulk update outstanding tickets, old Epic link, new SD Classification
•  SQL results now logged under ticket 

  Jira
  server Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key SD-23020

  Change result logging
•  Big Picture PROG-6 changes to assign only teams via Big Picture Home -Root = Bianca
•  Big Picture check teams for members and availability in Big Picture Home -Root = Rene
•  Process: Epic DoR / Epic value / Epic points / WSJF op epics (Arthur)
•  Process: where should we create epics? YPM or YIS? (Arthur, Benjamin)
•  Process: can we have a Yamaha-Team for PO's per product, to prioritise/prepare work? (Arthur, Benjamin)

...