Background
Users raise tickets for the cloud platform team to create a slack alert which sits in the Infra repository
Proposed user journey
The user raise a support ticket in our cloud-platform repository, this should contain the relevant data needed for the cloud-platform team member to create the alert and the contact for the use to message once completed
Approach
create a concourse job that will be triggered on the creation of these tickets, process the data and create/approve the pull request
- There should be some logic to capture and respond if the webhook isn't available
Which part of the user docs does this impact
Should create a new issues template to give the user more detail on this:
- include that they shouldn't raise until their webhook is in their namespace secrets, as in will fail
- to include an email or slack channel (depending on approach) so that we can message them their severity
Definition of done
Reference
How to write good user stories
Background
Users raise tickets for the cloud platform team to create a slack alert which sits in the Infra repository
Proposed user journey
The user raise a support ticket in our cloud-platform repository, this should contain the relevant data needed for the cloud-platform team member to create the alert and the contact for the use to message once completed
Approach
create a concourse job that will be triggered on the creation of these tickets, process the data and create/approve the pull request
Which part of the user docs does this impact
Should create a new issues template to give the user more detail on this:
Definition of done
Reference
How to write good user stories