You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 91
Next »
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

- 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]
STEP TO STEP GUIDE Team Yamaha to Yamaha Team:
- Edit Yamaha Team field configuration, Add all issue types and all IT project but YPM Project, Programme
Add Yamaha Team field to all screens where Team Yamaha is used.
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.
Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty, inform team leads to set Yamaha team field.
Connect Yamaha team field in Big Picture for YIS resource planning scrum teams.
Add team members scrum teams (Bianca/René, help of AJ?)
Check workflows/automation rules for Team Yamaha/Yamaha team CAB/YPM
- Set Yamaha team field required in YIS configuration scheme
- Set Yamaha team field required for other Dev, CAB scheme as well.
- Remove team Yamaha from screen in YIS.
RENE REQUIRED
YIS IMPROVEMENTS
JIRA IMPROVEMENTS
- Issue type description update
-
SD-27805
-
Getting issue details...
STATUS
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?
B2C-9698
-
Getting issue details...
STATUS
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
-
YIS-441
-
Getting issue details...
STATUS
-
YIS-438
-
Getting issue details...
STATUS
-
YM-686
-
Getting issue details...
STATUS
-
YIS-451
-
Getting issue details...
STATUS
-
YIS-449
-
Getting issue details...
STATUS
-
YIS-455
-
Getting issue details...
STATUS
-
YM-705
-
Getting issue details...
STATUS
-
YIS-437
-
Getting issue details...
STATUS
- 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
- YIS:
- PMO:
- 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
- Sample software project, not used - delete= YES = Bianca van der Meer
- Big Picture: