Versions Compared

Old Version 91

changes.mady.by.user Bianca van der Meer

Saved on

compared with

New Version Current

changes.mady.by.user Bianca van der Meer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Table of Contents

Info

The Jira/Confluence backlog has been moved to YIS - JIRA-APPS Scrum Board
If you have any questions regarding improvements on the backlog or a new improvement request, please contact a Jira administrator or join the Jira Community Chapter.

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



Newsletter

Last newsletter


Next newsletter 

Information Systems Division

New Features

  • Onboarding new procedure and workflow 
    Status
    colourYellow
    titleIN PROGRESS
  • Custom field: Yamaha Entity: Activated on SD Onboarding and YPM  
    Status
    colourYellow
    titleIn Progress
  • Custom field: Ticket group(s) multi select instead of Ticket group checklist
    Status
    colourYellow
    titleIn Progress

Improvements

  • Migration to YIS - BL 
    Status
    colourGreen
    titleReleased
  • Deactivated issue type Test in YPM
    Status
    colourGreen
    titleReleased

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 van der Meer 
  •  Add field options from BigPicture =  Bianca van der Meer 
  •  Link to screens =  Bianca van der Meer 
  •  Change Board filters to add new field in the selection.
  •  Migrate data for story level items - for matching options (bulk update) Bianca van der Meer / AJ van Spanje [AgileVisor] 
    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 Bianca van der Meer 
  •  Update Confluence, teams and dashboards (procedure) = Bianca van der Meer  
  •  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 van der Meer 
  •  YPM multi select for projects Bianca van der Meer 
  •  SD link screens to new Team Yamaha field (double maintenance for YIS issues) Bianca van der Meer 
    Image Removed
  •  YPM -  transition move to development board screen etc. Team select screen Bianca van der Meer 
  •  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

  •  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]
  •  NEW: Default Yamaha team on sub-tasks (from Dzmitry) Bianca van der Meer / AJ van Spanje [AgileVisor]

...

  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

YIS IMPROVEMENTS

JIRA IMPROVEMENTS

  •  Issue type description update 
  •  
    Jira
    serverJira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId2c81710b-ad02-31bf-9e7f-9678590354e2
    keySD-27805
    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?
    Jira
    serverJira
    serverId2c81710b-ad02-31bf-9e7f-9678590354e2
    keyB2C-9698
    Bianca van der Meer 
  •  Jira-test Incoming/Outgoing mail settings change : Bianca van der Meer  / Daan Delpeche [X]
  •  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
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYIS-441
      •  
        Jira
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYIS-438
      •  
        Jira
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYM-686
      •  
        Jira
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYIS-451
      •  
        Jira
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYIS-449
      •  
        Jira
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYIS-455
      •  
        Jira
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYM-705
      •  
        Jira
        serverJira
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId2c81710b-ad02-31bf-9e7f-9678590354e2
        keyYIS-437
    •  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

ARCHIVE OF WORK DONE

...

...