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

Compare with Current View Page History

« Previous Version 35 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 process update, multi select
  • 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
  • Update automation rules

RENE REQUIRED

  • 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

YIS IMPROVEMENTS

  • 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.
  • NEW: Can we have a "target release date" field in Jira?
  • NEW: Task type this is no new Yamaha Team field on creation, for Story, Spike types its in place (Dzmitry)
  • NEW: business value activeren op stories (Arthur)
  • NEW: Epic DoR / Epic value / Epic points / WSJF op epics (Arthur)
  • NEW: on closing pop-up, add mandatory fix/version field (from AJ)
  • NEW: Rename "Installation instructions" to "Code/Configuration Details" (From SF)
  • NEW: Defect has Generic Test WF assigned, instead of Generic Bug WF. Correct this? (From Diego email)
  • NEW: Default Yamaha team on sub-tasks (from Dzmitry)
  • NEW: Add Jira rights for PO & BA to set sprint goal (From SF)
  • NEW: "Done deployment" resolution is set for status "Done" illogically (From SF)
  • NEW: Spikes: can we please skip statusses in WF? (From SF)
  • Release numbers in versions = Marcel/AJ
  • Naming convention versions, in Confluence  Release numbering procedure= Marcel/AJ 
  • Split error YIS: solution group, Yamaha team
  • YIS default screen config clean up
  • YIS field config clean up
  • Test types/schermen clean up = AJ
  • YMPACT OMS move for issuetypes bug/defect
  • Worklog permissions
  • Disappearing comments pop-up
  • B2B bord transparancy = Mohan
  • 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

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


Confluence improvements

  • Jira confluence space: for YIS, YPM, intro
  • Confluence overview of spaces with owners
  • Condense information/spaces into logical topics


  • No labels