"service concerned" field not used in ticketing system (or gets lost)

[FlorianLudwig]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to My support tickets: https://www.ovh.com/manager/dedicated/#/support/tickets/new
2. topic = incident
3. product = "Managed kubernetes service"
4. A list appears "service concerned" - select any kubernetes cluster
5. 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

[JeremyDec]

Hello @FlorianLudwig

If I understand well, you suggest to retrieve the selected service, once you answer "No" to the question: "Have you found the answer to your question?", and then move to the page to fill Incident details ? (as in the following screen:

Jeremy

[FlorianLudwig]

@JeremyDec I do not know what the view is from the service is. But I fill out those questions like "cluster concerned" and then submit it. And get the response "please let know which cluster this is about so i can help you"... why did I filled out those questions?