Table of Contents

Jira improvements checklist

YAMAHA TEAMS CUSTOM FIELD

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

...

•  Remove Team Yamaha from screens
•  Remove Team Yamaha field from YIS-Boards in Issue Detail View AJ van Spanje [AgileVisor] 
•  Update Confluence, teams and dashboards (procedure) = Bianca van der Meer  / AJ van Spanje [AgileVisor] 
  
  
•  NEW: Default Yamaha team on sub-tasks (from Dzmitry) Inherit Yamaha Team Field,  Create separate field configuration, setup a post function for create subtask Bianca van der Meer / AJ van Spanje [AgileVisor]
  https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/68878488/Copy+field+value+from+parent+issue
  
•  ServiceDesk issuetypes process update, single select instead of multi select Bianca van der Meer 

RENE REQUIRED

•  Bugfix ticket creation and approval via SD (skip CAB) by PO, Deptmanagers, Teamlead 
•  Resolution stop using, set per project/workflow 
  •  Create list per project/workflow  YIS & development projects = Done & Canceled  Bianca van der Meer / AJ van Spanje [AgileVisor] 
  •  Review list per project/workflow   René van der Pal 
  •  SD resolution list = Rene, also to be discussed with BAU team/ SD Infra René van der Pal / Bianca van der Meer 
•  Remove/change resolutions from reporting
•  Jira admin changes communication = review Bianca van der Meer / René van der Pal 
•  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 (30 min meeting) Bianca van der Meer  / René van der Pal / Nico Meijer 
•  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 René van der Pal 
  •  Onboarding/offboarding → teams BP authorization check  global teams Bianca van der Meer 

YIS IMPROVEMENTS

•  J-sox
  
  •  YIS- integrate Infrastructure, including J-sox approval workflow (currently included in SD Default Workflow) Bianca van der Meer AJ van Spanje [AgileVisor] 
  •  Add validation for deploymentapprovers group for status to done deployment Bianca van der Meer 
•  Training material Jira AJ van Spanje [AgileVisor]/ Bianca van der Meer / Sreyasi Das [Incrementor] 
•  NEW: Add Jira rights for PO & BA to set sprint goal (From SF)
  •  YIS PO/SM/Dev access rights draft - AJ: project roles exist and are assigned to logical rights in permission scheme.
  •  User group YMEUACJiraProductOwners added in all Jira IS projects as role for Start/Stop and manage sprint permissions - Bianca van der Meer 
•  CLEANUP / USABILITY
  •  YIS default screen config clean up
  •  YIS field config clean up
  •  On closing pop-up, add mandatory fix/version field (from AJ) AJ van Spanje [AgileVisor] 
  •  Disappearing comments pop-up
  •  Split error YIS: solution group, Yamaha team
  •  BEW: Subtask to inherit team name!!!
  •  custom fields to local contexts
  •  Worklog permissions 
  •  YIS-Boards Issue Detail view
  •  YIS-Boards Card layout
•  DoD required / UAT / on epic? 
  •  Only on issue type when used (scheduled for deployment)  AJ van Spanje [AgileVisor]/ Bianca van der Meer 
  •  DOD project = team → Confluence Bianca van der Meer
  •  DOD Projects= review Bianca van der Meer / AJ van Spanje [AgileVisor]  
•  Epics process
  •  create meaningful epics WF (Arthur) AJ van Spanje [AgileVisor] 
  •  Epic points / WSJF op epics (Arthur) AJ van Spanje [AgileVisor] 
  •  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. AJ van Spanje [AgileVisor] 
  •  Can we have a Yamaha-Team for PO's per product, to priorities/prepare work? (Arthur le Blanc, Benjamin Smits, Stefano Arzuffi, Marc de Graaf) Salesforce-POs Bianca van der Meer / AJ van Spanje [AgileVisor] 
•  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

  Approved by René  AJ van Spanje [AgileVisor]  / Bianca van der Meer  
  •  https://marketplace.atlassian.com/apps/1222051/status-time-free?hosting=datacenter&tab=overview install addon Bianca van der Meer 
  •  Reporting /addon use instructions
  •  NEW: Review addon limitation of use AJ van Spanje [AgileVisor] 
    
•  YIS board transitions - AJ van Spanje [AgileVisor] 
  
  •  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
    •  YMPACT OMS move for issuetypes bug/defect Bianca van der Meer / AJ van Spanje [AgileVisor] 
  •  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
•  Installation instructions 
  •  Location of installation instructions → impossible. Let's remove the default text instead AJ van Spanje [AgileVisor] 
  •  Installation instructions local context? Does Ympact use this? - AJ van Spanje [AgileVisor]  (Rob de Vries rob.devries@yamaha-motor.nl) → Ympact does use this. Cannot limit to local
  •  Rename "Installation instructions" to "Code/Configuration Details" (From SF) Check with Ympact team, EPAM - AJ van Spanje [AgileVisor] 
•  Releases:
  
  •  NEW: Can we have a "target release date" field in Jira? (SF team) - AJ van Spanje [AgileVisor] 
  •  Release numbers in versions = Marcel/AJ
  •  Naming convention versions, in Confluence  Release numbering procedure Marissa Smit  / AJ van Spanje [AgileVisor]   Release preparation
  •  Target release date global context? Marissa Smit
  •  Make Release preparation easy to find in Confluence 
  •  Release documentation condensation in Confluence  Marissa Smit 
    •  Release numbering procedure ( B2B- Java procedure only) 
    •  How-to Manage versions  (Jira instructions)
    •  Release management procedure (B2B instructions per product)
    •  Version Control
    •  Release preparation  (B2C- procedure only)
  •  Fix/version use? Limit to release managers? - Marissa Smit 
  •  Affected version/s System Field add to screens for YIS  AJ van Spanje [AgileVisor] 
•  Test types/screens investigation AJ van Spanje [AgileVisor] 
  •  Investigation AJ van Spanje [AgileVisor] 
  •  Test types clean up?: sub-test execution & test setAJ van Spanje [AgileVisor] 
  •  Standardise field order on test screens?AJ van Spanje [AgileVisor] 
  •  Remove fix/version from test screens? (Alexa) AJ van Spanje [AgileVisor] 
  •  NEW: Add "Sprint" field to all test type screens (Grzegorz)

JIRA GLOBAL IMPROVEMENTS

•  Bugfix ticket creation and approval via SD (skip CAB) by PO, Dept. managers, Teamlead, Select Jira-Project, Yamaha Team
•  Version Manager for Jira  app compatible with Data Center
  “As a small vendor, I have decided to not go through the effort of Data Center certification by Atlassian. However, the Version Manager for Jira addon works perfectly fine with Jira Data Center, is fully supported from my side for Data Center and quite some customers are using it in Jira Data Center successfully. You can safely use it in Jira Data Center. “
  •  Install on Jira-test, check if it is working as expected Bianca van der Meer 
  •  Contact Avisi for AFOS migration if app can be used Bianca van der Meer 
•  Version manager access BA & Release manager
•  Board admin access, Scrum master
•  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
    •  

      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 field to single select SD classification Bianca van der Meer 
    Added: compliancy en business improvements 
    Operational Activities is changed to Business as usual (BAU)
    Ympulse- Operational activities change all to Business as usual (BAU)
    
    
    •  Start with new tickets
    •  Automation rules; create, copy from etc.
      •  

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

      •  

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

    •  Workflows
    •  Filters
    •  Dashboards
    •  Boards
    •  Bulk update outstanding tickets, old Epic link, new SD Classification
•  Issue type description update 
•  

  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-27805

  Component as systems  remove from screens Bianca van der Meer 
  •  Empty component fields, move to custom field Portfolio 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?

  Jira
  server Jira serverId 2c81710b-ad02-31bf-9e7f-9678590354e2 key B2C-9698

  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
•  Fix version required for epics? Check all workflows where required, still needed?
•  PMO- YIS Deliverables, move to YIS?  or adjust all SCRUM boards to include to see full workload of the team (Tania)
  •  Adjusted Wolverine and DAYCARE board to include Deliverables Bianca van der Meer 
•  PMO-YIS EPIC creation, not clear for the teams (Tania)
•  YPM multi select for projects, keep Team Yamaha or create new field? Bianca van der Meer / AJ van Spanje [AgileVisor] 

ARCHIVE OF WORK DONE 

•  YIS:
  •  Workflow cleanups YIS:
    •  NEW: Defect has Generic Test WF assigned, instead of Generic Bug WF. Correct this? (From Diego email) - AJ van Spanje [AgileVisor] 
    •  NEW: "Done deployment" resolution is set for status "Done" illogically (From SF) - Bianca van der Meer 
    •  NEW: Spikes: can we please skip statusses in WF? (From SF) - AJ van Spanje [AgileVisor] 
    •  Move bug & defect to Development flow - needs communication AJ van Spanje [AgileVisor] 
    •  Move Test issuetypes to Subtask flow - needs communication AJ van Spanje [AgileVisor] 
    •  Move Epics to Subtask flow - needs communication AJ van Spanje [AgileVisor] 
    •  Rename Subtask flow to Simpe 4-step flow AJ van Spanje [AgileVisor] 
  •  Location of acceptance criteria → impossible. Let's deactivate acceptance criteria for this reason, and use Description instead. AJ van Spanje [AgileVisor] 
  •  Create/correct new YIS boards (template/filter) - AJ van Spanje [AgileVisor] 
    •  B2B bord transparancy = Mohan - AJ van Spanje [AgileVisor] 
    •  Scrum & Kanban template AJ van Spanje [AgileVisor] 
      •  Marvels epic needs to be removed → Show Rene first AJ van Spanje [AgileVisor] 
      •  Marvels old scrum needs to be removed → Show Rene first AJ van Spanje [AgileVisor] 
    •  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] 
    •  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 van Spanje [AgileVisor] 
    •  Setup Wolverine scrum for Tania https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=107&view=planning&issueLimit=100  AJ van Spanje [AgileVisor] 
    •  Setup Daycare scrum for Tania https://support.yamnet.com/secure/RapidBoard.jspa?rapidView=108&view=planning.nodetail&issueLimit=100 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 & Tania
•  PMO:
  •  NEW: business value activeren op stories (Arthur) - AJ van Spanje [AgileVisor] 
  •  NEW: business value activeren op epics (Arthur) - AJ van Spanje [AgileVisor] 
    
    
•  Other JIRA-projects
  •  New Issue type Defect and Change Request for all development projects, yes = Bianca van der Meer 
    Issue type Defect and Change request added to
    
    
    Already used in YIS
    
  •  Workflow had to be changed, resolution must be empty for Bitbucket/ Jenkins pull request else a warning is generated. Bianca van der Meer 
    •  Generic Bug Workflow Added status Scheduled for deployment, Added transition To scheduled for Deployment,  condition added empty resolution field.
    •  Generic Development Workflow V2Generic 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
      
•  Sample software project, not used - delete= YES  = Bianca van der Meer 
•  Automation rules, change Global to projects Bianca van der Meer 
  
•  Big Picture:
  •  Bigpicture cleanup: team only setup in Root, then assigned in PROG Bianca van der Meer 
•  Archive Jira Project 'Future requirements', Close 5 outstanding stories René van der Pal / Bianca van der Meer 

...

•  Update automation rules add Yamaha Team field 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 - JAVA APPLICATION deployment approval requests

  •  

    SD - JAVA APPLICATION deployment approval requests DMS projects

  •  

    SD - JAVA APPLICATION deployment approval requests e-Invoice projects

  •  

    SD - JAVA APPLICATION deployment approval requests Invoice projects

  •  

    SD - JAVA APPLICATION deployment approval requests YMPULSE and YAMCOM

  •  

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

  •  

    PFB - Move deliverable to development board

  •  CAB Create Development Issue (and link back to SD issue)
  •  

    CAB - Create TST issue after creation of linked DEV issue

  •  

    SD - Create elevated user rights request

  •  

    PFB - Create deliverables in PFB Project or Epics

  •  

    OMS interactive deployment request

  •  

    OMS normal - scheduled deployment request

  •  

    Projects - Create TEST story in development Project (Added Yamaha team)

  •  

    SD - Create RobotJob change request ticket

  •  

    SD Create Onboarding tickets for departments YME-Facility is not yet used as official team

•  Set Yamaha team field required in YIS configuration scheme
•  Set Yamaha team field required for other Dev, CAB scheme as well.
•  Change (YIS) Board filters to  delete Team Yamaha field in selection and quickfilters Bianca van der Meer / AJ van Spanje [AgileVisor] 
•  NEW: Task type this is no new Yamaha Team field on creation, for Story, Spike types its in place (Dzmitry) Bianca van der Meer / AJ van Spanje [AgileVisor]

Confluence improvements checklist

Spaces

•  Confluence spaces organization/overview Bianca van der Meer 
•  Ownership/content mgr Bianca van der Meer 
•  Condense spaces into logical topics Bianca van der Meer / AJ van Spanje [AgileVisor] 
•  YIS space
  •  YIS/ YPM intro Bianca van der Meer / AJ van Spanje [AgileVisor] 
•  Reorganize User Manuals (Public) remove departments but only include products/applications  Bianca van der Meer 
•  Atlassian space redesign? Bianca van der Meer / AJ van Spanje [AgileVisor] 
•  SD-33871 - Confluence after login search bar is not visible IN PROGRESS Check after migration to AFOS if this is still an issue Bianca van der Meer 

...

•  Atlassian space add Jira basic instructions AJ van Spanje [AgileVisor] 
  •  Issue type overview + description AJ van Spanje [AgileVisor]  (already done in Jira)
•  Where to store Team information? General Information Systems Division? Bianca van der Meer / AJ van Spanje [AgileVisor] 
  •  Create template for (YIS) teams Bianca van der Meer / AJ van Spanje [AgileVisor] 
•  Move pages from General to General Information Systems Division  and informal all users Bianca van der Meer 

ARCHIVE OF WORK DONE

•  Delete space Technical Documentation Bianca van der Meer 
•  Delete space Source MS-SQL scripts move one page MS-SQL Scripts to General IS space Bianca van der Meer 
•  Create new General Information Systems Division space Bianca van der Meer