"service concerned" field not used in ticketing system (or gets lost)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 285
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 49
Description
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
- Go to My support tickets: https://www.ovh.com/manager/dedicated/#/support/tickets/new
- topic = incident
- product = "Managed kubernetes service"
- A list appears "service concerned" - select any kubernetes cluster
- Continue ticket creation process. The information selected under "service concerned" does not end up in the final ticket and will get asked again by support. (And then the name of the project will be asked) This takes time while there is an incident that could have been spent actually working on the issue.
Expected behavior
The "service concerned" field is submitted to support. This should include the id and name of the cluster as well as the project id.
Screenshots
image
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue from the My support tickets URL using an incident for a Managed Kubernetes service and selecting a cluster under “service concerned.” Trace the ticket-creation flow to determine where the selected cluster and project information is lost; done means the final support ticket includes the cluster id and name and the project id without asking support to collect them again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100