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

RENE REQUIRED

•  Resolution stop using, set per project/workflow
•  Remove resolutions from reporting
•  Component as systems = Rene
•  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
•  Jira admin changes communication = review
•  Sample software project, not used - delete? = Rene
•  DoD required / UAT / on epic? = Rene/Nils
•  New Issue type Defect and Change Request for all development projects

...

YIS IMPROVEMENTS

•  Release numbers in versions = Marcel/AJ
•  Naming convention versions, in Confluence  Release numbering procedure= Marcel/AJ 
•  Location of acceptance criteria
•  Location of installation instructions
•  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

...

JIRA IMPROVEMENTS

•  Issue type description update