Page History

...

•  Create custom field in Jira, single select: Yamaha Team Bianca van der Meer 
•  Add field options from BigPicture =  Bianca van der Meer 
•  Link to screens =  Bianca van der Meer 
•  Change Board filters to add new field in the selection.
•  Migrate data for story level items - for matching options (bulk update) Bianca van der Meer / AJ van Spanje [AgileVisor] 
  Implement only for YIS, later for other projects. Remove Team Yamaha label field, copy all first selected teams to new field
        23-08-2022
  •  DMS - story
  •  DAYCARE  all issues
  •  YAMALUBE = story only
  •  Correct issuetypes with Yamaha Teams
  •  Reindex
  •  IN PROGRESS AJ: DMS all, SF all, daycare, marvels, wolverine, b2b-as400
  •  NO CONTENT: HIQ
•  Migrate data for epic level items = PO's to deduplicate team options
•  BigPicture interface mapping to new field Bianca van der Meer 
•  Update ConfluenceConfluence 
•  Migrate data for story level items - for not matching options = PO's/managers
•  ServiceDesk issuetypes  update Yamaha team add to fields 
  •  ServiceDesk issuetypes process update, single select instead of multi select = Bianca
•  YPM multi select for projects
•  SD link screens to new Team Yamaha field (double maintenance for YIS issues)
  
  
•  YPM -  transition move to development board screen etc. Team select screen
•  Update filters → used in dashboards SD teams
•  Update automation rules Bianca van der Meer 
  •  

    SD_B2B Update solution group, Team Yamaha for issues received by email

  •  

    SD_B2C Update solution group, Team Yamaha for issues received by email

  •  SD SD_INFRA Update solution group, Team Yamaha for issues received by email
  •  

    SD Create Onboarding tickets for departments

  •  

    SD Update Epic Link and yamaha team based upon application choice user (create issue event)

  •  

    SD Update solution group, Yamaha Team based upon application and wrong department

  •  

    SD User Offboarding Update issue fields when request received by email

  •  

    SD User Onboarding Update issue fields when request received by email

  •  

    SD - Create JSOX-CHANGE authorization tickets out of Infra for management

  •  

    SD - Create JSOX authorization tickets out of AS400 for management

  •  

    SD - Create JSOXM / TASK / INC authorization tickets out of AS400 for management

  •  

    SD - YAMS and YMPACT deployment approval requests

  •  

    SD Auto close unauthorized e-mail requests and categorize authorized senders

  •  

    PFB - Move deliverable to development board

•  NEW: Task type this is no new Yamaha Team field on creation, for Story, Spike types its in place (Dzmitry)
•  NEW: Default Yamaha team on sub-tasks (from Dzmitry)

...

•  Resolution stop using, set per project/workflow 
  •  Create list per project/workflow = Bianca van der Meer 
  •  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 van Spanje [AgileVisor]  / Bianca van der Meer  /Revathi
•  Jira admin changes communication = review
•  DoD required / UAT / on epic? = Rene/Nils/ AJ van Spanje [AgileVisor] 
  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 van der Meer 
  •  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 van der Meer 
•  Big Picture check teams for members and availability in Big Picture Home -Root = Rene
•  Process: create meaningful epics WF (Arthur)
•  Process: Epic points / WSJF op epics (Arthur)
•  Process: where should we create epics? YPM or YIS? (Arthur, Benjamin) Bjorn says there is no standard. B2B uses YPM, B2C uses B2C. And no owner who can decide on this.
•  Process: can we have a Yamaha-Team for PO's per product, to prioritise/prepare work? (Arthur, Benjamin) Salesforce-POs

...

•  Correct new YIS boards (template/filter) - AJ van Spanje [AgileVisor] 
  •  Scrum & Kanban template
    •  Marvels epic needs to be removed → Show Rene first
    •  Marvels old scrum needs to be removed → Show Rene first
  •  Create kanban board template = HIQ → REVIEW  Bianca van der Meer 
  •  Java kanban board needs template + filters → move to template AJ : New board AJ van Spanje [AgileVisor] 
  •  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 van Spanje [AgileVisor] 
  •  All test boards need to be made standard or removed - investigation Andrzej - confirmed - AJ
  •  Ympact team kanban board
    •  Fix Ympact board filter to include team name
    •  Create new Ympact kanban board
    •  Remove old Ympact kanban board
    •  Create Ympact scrum board ON HOLD
  •  Logistics team kanban board 
    •  Fix Logistics board filter to include team name
    •  Create new kanban (template)
    •  Remove old kanban (non-template)
    •  Create Ympact scrum board 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
•  Installation instructions
  •  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) → Ympact does use this. Cannot limit to local
  •  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/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
•  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
  •  BEW: Subtask to inherit team name!!!
•  Test types/screens investigation = AJ
  •  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
•  Add validation for deploymentapprovers group for status to done deployment= Bianca
•  YIS- integrate Infrastructure, including J-sox approval workflow (currently included in SD Default Workflow)

...