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

Compare with Current View Page History

« Previous Version 136 Next »

YAMAHA TEAMS

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

STEP TO STEP GUIDE Team Yamaha to Yamaha Team:

  • Communicate upcoming change to Information Systems teams including EPAM Team Yamaha → Yamaha Team
    • ServiceDesk issuetypes process update, single select instead of multi select Bianca van der Meer 
  • Custom field configuration Yamaha Team, Create custom field in Jira, single select: Yamaha Team Bianca van der Meer 
    • Add field options from BigPicture  to Yamaha Team  Bianca van der Meer 
    • Add all IT projects, used Issue types but Programme and Project
  • Link to screens =  Bianca van der Meer 
    • SD link screens to new Team Yamaha field (double maintenance for YIS issues) Bianca van der Meer 
    • YPM -  transition move to development board screen etc. Team select screen Bianca van der Meer 
  • Change Board filters to add new field in the selection Bianca van der Meer / AJ van Spanje [AgileVisor] 
  • Edit Yamaha Team field configuration, Add all issue types and all IT project but YPM Project, Programme Bianca van der Meer / AJ van Spanje [AgileVisor] 
  • Add Yamaha Team field to all screens where Team Yamaha is used.
  • Re-index projects

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

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

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

  • Connect Yamaha team field in Big Picture for YIS resource planning scrum teams Bianca van der Meer 

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

  • Check workflows/automation rules for Team Yamaha/Yamaha team CAB/YPM

  • Set Yamaha team field required in YIS configuration scheme
  • Set Yamaha team field required for other Dev, CAB scheme as well.
  • Change Board filters to add delete Team Yamaha field in the selection Bianca van der Meer / AJ van Spanje [AgileVisor] 
  • Update filters → used in dashboards SD teams Bianca van der Meer 
  • 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

  • Remove team Team Yamaha from screens



Yamaha Team

  • B2B-ANALYSTS 2639
  • B2B-APPS-BAU 9364
  • B2B-AS400 943
  • B2B-BI 633
  • B2B-LOGISTICS 1158
  • B2B-SOFTWAYIT
  • B2B-TM1
  • B2B-XICERO
  • B2B-YAMS
  • B2C-AEM-CAAS 904
  • B2C-APPS-BAU
  • B2C-DIGITALUM
  • B2C-EPAM-BAU 3969
  • B2C-EPAM-MOTORS
  • B2C-EPAM-WAVERUNNERS 1004
  • B2C-SALESFORCE-CRM 1064
  • B2C-SF-SCRUM → CRM-KANDO
  • DAYCARE
  • DMS → AVENGERS
  • HIQ
  • HIQ-BAU
  • INFRA
  • INFRA-AS400
  • INFRA-SD
  • JIRA-APPS
  • MARVELS
  • PMO
  • PO-SALESFORCE (not in Big Picture)
  • WOLVERINE
  • YAMALUBE
  • YMF-IS

RENE REQUIRED

YIS IMPROVEMENTS

JIRA GLOBAL IMPROVEMENTS

  • 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 / AJ van Spanje [AgileVisor] 
    • 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 field to single select SD classification  or components field Bianca van der Meer 
      • Start with new tickets
      • Automation rules; create, copy from etc.
      • Workflows
      • Filters
      • Dashboards
      • Boards
      • Bulk update outstanding tickets, old Epic link, new SD Classification
  • Issue type description update 
  • SD-27805 - Getting issue details... STATUS Component as systems  remove from screens Bianca van der Meer 
  • Bigpicture cleanup: team only setup in Root, then assigned in PROG Bianca van der Meer 
  • Req. SQL approval, new issue same like req. job change request & add functionality to DEV projects  Bianca van der Meer 
  • NEW: on B2C project fix/version isn't mandatory? B2C-9698 - Getting issue details... STATUS Bianca van der Meer 
  • Jira-test Incoming/Outgoing mail settings change : Bianca van der Meer  / Daan Delpeche [X]
  • Jira-production Incoming/Outgoing mail settings change Bianca van der Meer / Daan Delpeche [X] 
  • Jira-production  Incoming/Outgoing mail settings setup PACS

ARCHIVE OF WORK DONE

Done before  



  • No labels