Page History
...
-
Check workflows/automation rules for Team Yamaha/Yamaha team CAB/YPM
- Delete Yamaha team form all Workflows, Yamaha team/team Yamaha required (JSU validator)
- Update filters → used in dashboards SD teams Bianca van der Meer
- Update automation rules remove team Yamaha 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
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 - Move deliverable to development board
-
PFB - Create deliverables in PFB Project or Epics
-
- Remove Team Yamaha from screens
- Remove Team Yamaha field from YIS-Boards in Issue Detail View AJ van Spanje [AgileVisor]
- Update Confluence, teams and dashboards (procedure) = Bianca van der Meer / AJ van Spanje [AgileVisor]
- NEW: Default Yamaha team on sub-tasks (from Dzmitry) Inherit Yamaha Team Field, Create separate field configuration, setup a post function for create subtask Bianca van der Meer / AJ van Spanje [AgileVisor]
https://innovalog.atlassian.net/wiki/spaces/JMWE/pages/68878488/Copy+field+value+from+parent+issue - ServiceDesk issuetypes process update, single select instead of multi select 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 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
-
- 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]
...
Overview
Content Tools