Table of Contents

Jira Chapter 

The Jira Chapter meetings are canceled, due to overlap with other meetings where  Jira/Confluence is also discussed as a topic, such as Scrum Chapter.

The following proposal has been agreed on 1-2-2023 with attendees in the Jira Chapter meeting:

• A workshop will be arranged once every 2 to 3 months in which a clear agenda with topics is presented.
  Anyone from Information Systems Division can join when interested and request topics (questions/improvements/adjustments) by the Jira administrator to be added to the workshop agenda.
• Jira changes will be updated in the manuals, if there is any unclarity, reference can be made to the training material. If not found ask Jira administrator to explain.
• Suggestions for improvement/adjustments can be discussed within the teams.
  The scrum masters can ask the Jira administrator to add a PBI (product backlog item) in the Jira Board.
• The Jira administrator will join the Scrum Master chapter on regular basis and can be invited when Jira/Confluence topics are on the agenda of any other meeting as well.

Communication

• Updates can be send in a newletter via e-mail with the higlights of updates and Jira fields changes including a reference to the training material.
• Include Jira/Confluence as topic in the Townhall meeting.
• Planned maintenance will be informed via banner in Jira and the customer portal(s) and in the Jira Maintenance Teams group.
• Jira/Confluence information regarding unexpected situations is sent by email and, if possible, communicated via banner in Jira/Confluence and the Jira customer portal(s).

FAQ

• How can I learn more about past changes? We advise you to read the Jira Training and Confluence Training materials, or dive into tickets resolved in past Jira sprints: ’22 Jira apps – S2’ ’22 Jira apps – S3’ etcetera.
• How can I learn more about upcoming changes? We advise you to check the short term planning here: YIS- JIRA-APPS Scrum board or the long term planning here: Roadmap Jira/Confluence/Bitbucket.
• How can I bring my brilliant improvement idea for Jira/Confluence or Bitbucket to the Jira team? Reach out to a Jira admin via MS Teams or e-mail, for Bitbucket please reach out to Marcel Smit. 
• How can I ask support for Jira, Confluence or Bitbucket? Please raise a ticket for Infra Servicedesk via the Jira Customer Portal

Newsletter

Last newsletter

• Information Systems Division 07 Mar 2023  Jira_Confluence_Bitbucket updates Q1 2023.msg
• YME P&A: 07 Mar 2023  Jira_Confluence_Bitbucket updates Q1 2023.msg
• Compliance: 07 Mar 2023 Jira_Confluence_Bitbucket updates Q1 2023.msg

Next newsletter 

Information Systems Division

New Features

• Onboarding new procedure and workflow 

  Status
  colour Yellow title IN PROGRESS

• Custom field: Yamaha Entity: Activated on SD Onboarding and YPM  

  Status
  colour Yellow title In Progress

• Custom field: Ticket group(s) multi select instead of Ticket group checklist

  Status
  colour Yellow title In Progress

Improvements

• Migration to YIS - BL 

  Status
  colour Green title Released

• Deactivated issue type Test in YPM

  Status
  colour Green title Released

Fixes

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
  •  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
•  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)
  Image Removed
  
•  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

  •  

    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)

...

1. Edit Yamaha Team field configuration, Add all issue types and all IT project but YPM Project, Programme

2. Add Yamaha Team field to all screens where Team Yamaha is used.

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

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

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

6. Connect Yamaha team field in Big Picture for YIS resource planning scrum teams. 

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

8. Check workflows/automation rules for Team Yamaha/Yamaha team CAB/YPM

9. Set Yamaha team field required in YIS configuration scheme
10. Set Yamaha team field required for other Dev, CAB scheme as well.
11. Remove team Yamaha from screen in YIS.

RENE REQUIRED

•  Scrum & Kanban template
  •  Marvels epic needs to be removed → Show Rene first
  •  Marvels old scrum needs to be removed → Show Rene first
•  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 

  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/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
    •  

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

...

•  Create kanban board template = HIQ → REVIEW 
•  Java kanban board needs template + filters → move to template AJ : New board
•  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
•  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 → scrum 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 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

...

•  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?

...

•  YIS PO/SM/Dev access rights draft - AJ
•  User groups - Bianca

...

•  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)

...

•  NEW: business value activeren op stories (Arthur) - AJ
•  NEW: business value activeren op epics (Arthur) - AJ

...

•  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!!!

...

•  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)

...

JIRA IMPROVEMENTS

...

...

•  Empty component fields, move to custom field Portfolio = Bianca

...

...