You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 59 Next »

YAMAHA TEAMS

Single select field needed on sub-task/story/epic level. Projects will keep the old label field.

  • Create custom field in Jira, single select: Yamaha Team =  Bianca
  • Add field options from BigPicture =  Bianca
  • Link to screens =  Bianca
  • Change Board filters to add new field in the selection.
  • Migrate data for story level items - for matching options (bulk update)
    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
  • Migrate data for epic level items = PO's to deduplicate team options
  • BigPicture interface mapping to new field
  • Update Confluence
  • 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

    • 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

  • 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)
  • Jira-test Incoming/Outgoing mail settings change : Bianca / Daan Delpeche

RENE REQUIRED

  • Scrum & Kanban template
  • 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  SD-35530 - Getting issue details... STATUS = 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
      • YIS-441 - Getting issue details... STATUS
      • YIS-438 - Getting issue details... STATUS
      • YM-686 - Getting issue details... STATUS
      • YIS-451 - Getting issue details... STATUS
      • YIS-449 - Getting issue details... STATUS
      • YIS-455 - Getting issue details... STATUS
      • YM-705 - Getting issue details... STATUS
      • YIS-437 - Getting issue details... STATUS
    • 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  SD-23020 - Getting issue details... STATUS 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
  • NEW: Epic DoR / Epic value / Epic points / WSJF op epics (Arthur)

YIS IMPROVEMENTS

  • Correct new YIS boards (template/filter) - AJ
  • 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) → Ympact does use this.
    • 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
  • 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
    • BEW: Subtask to inherit team name!!!
  • 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
  • YIS- integrate Infrastructure, including J-sox approval workflow (currently included in SD Default Workflow)

JIRA IMPROVEMENTS

  • Issue type description update 
  • SD-27805 - Getting issue details... STATUS Component as systems  remove from screens =Bianca
    • Empty component fields, move to custom field Portfolio = Bianca
  • Sample software project, not used - delete= YES  = Bianca
  • New Issue type Defect and Change Request for all development projects, yes = Bianca
    Issue type Defect and Change request added to


    Already used in YIS
  • Bigpicture cleanup: team only setup in Root, then assigned in PROG = Bianca
  • Req. SQL approval, new issue same like req. job change request & add functionality to DEV projects = Bianca
  • NEW: on B2C project fix/version isn't mandatory? B2C-9698 - Getting issue details... STATUS


  • No labels