Page History
...
| Info |
|---|
The Jira/Confluence backlog has been moved to Jira Apps YIS - JIRA-APPS Scrum Board |
Jira
...
Biweekly meeting: Wednesday 10:00-10:55
Location: At the office/via teams
Community of Practice goal: To develop the quality & ease of use of Jira & obtain alignment across the organization.
Meeting goals:
...
Regular attendees:
- Bianca van der Meer – Jira admin & Practice lead
- AJ van Spanje – Scrum process facilitator & Jira admin
- Sreyasi Das – PMO process facilitator
Other attendees can join when interested, this also includes EPAM and other support partners working for Yamaha Information Systems Division.
After the Jira COP meeting the Jira Apps Backlog will be updated.
...
- Process alignment: Bugfix ticket creation and approval via SD (CAB can be skipped) by PO, Deptmanagers, Teamlead : Jira COP
- 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
- Secure admin app, limit admin access for Infra SD for User management only René van der Pal PO can be requested.
- Version manager, who can have access? Scrum master, PO, Release manager, Dept. manager/ team lead ?
Jira improvements checklist
JIRA GLOBAL IMPROVEMENTS
- PMO- YIS Deliverables, move to YIS? or adjust all SCRUM boards to include to see full workload of the team (Tania)
- PMO-YIS EPIC creation, not clear for the teams (Tania)
JIRA 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
- 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: BAU + eBikes + WaveRunners
- Adjusted Wolverine and DAYCARE board to include Deliverables Bianca van der Meer
PMO
- NEW: business value activeren op stories (Arthur) - AJ van Spanje [AgileVisor]
- NEW: business value activeren op epics (Arthur) - AJ van Spanje [AgileVisor]
JIRA GLOBAL IMPROVEMENTS
...
- Bigpicture cleanup: team only setup in Root, then assigned in PROG Bianca van der Meer
...
- 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
...
- 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
- Install trial version in Production & inform users./ Bianca van der Meer
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
- status-time-free install addon Bianca van der Meer
- Reporting /addon use instructions
- NEW: Review addon limitation of use AJ van Spanje [AgileVisor]
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
- 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
- Adjust select list René van der Pal
Added: compliancy and business improvements
Operational Activities is changed to Business as usual (BAU)
Ympulse- Operational activities change all to Business as usual (BAU) - Discuss with Dept. managers and Team lead for change for BAU-Operational Activities Bianca van der Meer
- 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
- Version Manager for Jira app for Jira to limit access for Version manager only instead of Project admin access René van der Pal
...
YAMAHA TEAM
...
- Add field options from BigPicture to Yamaha Team Bianca van der Meer
- Add all IT projects, used Issue types but Programme and Project
...
- 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
...
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. → remainder Patrick/Rene
Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty, inform team leads to set Yamaha team field. → remainder Patrick/Rene
Yamaha Team
- B2B-ANALYSTS 2639 Bianca van der Meer issuetype not in (Programme, Project) and "Yamaha Team" is empty and "Team Yamaha" = "team#B2B-ANALYSTS" and assignee is empty, 3 left to which team to be assigned René van der Pal
- B2B-APPS-BAU 9364 Bianca van der Meer
- B2B-AS400 943 Bianca van der Meer
- B2B-BI 633 multiple entries done
- B2B-LOGISTICS 1158 multiple entries done
- B2B-SOFTWAYIT
- B2B-TM1
- B2B-XICERO
- B2B-YAMS
- B2C-AEM-CAAS 904 multiple entries remaining
- B2C-APPS-BAU multiple entries remaining
- B2C-DIGITALUM multiple entries remaining
- B2C-EPAM-BAU 3969 multiple entries remaining
- B2C-EPAM-MOTORS multiple entries remaining
- B2C-EPAM-WAVERUNNERS 1004 multiple entries remaining
- B2C-SALESFORCE-CRM 1064
- B2C-SF-SCRUM → CRM-KANDO
- DAYCARE → WOLVERINE/YAMALUBE
- DMS → AVENGERS
- HIQ
- HIQ-BAU
- INFRA
- INFRA-AS400 Bianca van der Meer
- INFRA-SD Bianca van der Meer
- JIRA-APPS
- MARVELS
- PMO
- PO-SALESFORCE (not in Big Picture)
- WOLVERINE
- YAMALUBE
- YMF-IS
- Tickets with multiple entries Bianca van der Meer
...
Connect Yamaha team field in Big Picture for YIS resource planning scrum teams 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]
- YPM Multi select Yamaha Team(s) field for Programme and Project, EPIC, Enhancement Bianca van der Meer / AJ van Spanje [AgileVisor]
...
CONFLUENCE 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
- New Jira portal instructions including guide for Information Systems & P&A Customer support
- Restructure Page tree in Atlassian Space Bianca van der Meer
- 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
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 Jira_Confluence_Bitbucket updates Q1 2023.msg
- YME P&A: Jira_Confluence_Bitbucket updates Q1 2023.msg
- Compliance: 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
Overview
Content Tools