-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template issue when trying to open an Incident #3048
Comments
👋 Thank you for opening your first issue. I'm just an automated bot that's here to help you get the information you need quicker, so please ignore this message if it doesn't apply to your issue. |
Can you share your log file after replicating this bug please. |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
Sorry for the late response.
|
Sorry @Unbr8kable that’s not the right log. You can find it in |
Oh sry.
|
Oh... this was fixed in v2.4 are you sure you’re on v2.3? If so, I’ll port the fix. |
Yes i am sure. Is v2.4 currently released? |
v2.4 (which will become v3.0, see #2943) is currently in development. Can you share the request you're making? |
What do you mean with „share the request“? |
@Unbr8kable you sent an HTTP request to the API. We'd need this exact request to reproduce it on our own machines. The request includes the URL, headers, and body. You should just remove your real API key, of course. |
Hi, curl -H "Content-Type: application/json;" -H "X-Cachet-Token: abcdef" --data '{"name":"Downtime","status":2,"visible":1,"component_id":1,"component_status":2,"template":"That is a Template"}' www.ghijklmn.de/api/v1/incidents |
@Unbr8kable I've not tested your request yet, but I've read a documentation I was writing, and the |
Thats right, the message parameter is missing, we some templates for different incidents. When I post an incident with a template without spaces, e.g. thisisatemplate, this error message doesnt appear. |
Ok I've just tested your request. curl -H "Content-Type: application/json;" -H "X-Cachet-Token: kHgFghvC42H" \
--data \
'{"name":"Downtime","status":2,"visible":1,"component_id":1,"component_status":2,"template":"ThatisaTemplate"}' \
http://cachet.local/api/v1/incidents I have this error {"errors":[{"id":"5230d04c-a524-48cc-af7e-84d50ebde465","status":400,"title":"Bad Request","detail":"The request cannot be fulfilled due to bad syntax.","meta":{"details":["The message field is required."]}}]} Please note that the "template" field is supposed to be a template slug. So, it's not supposed to contains spaces. |
Thanks @anthonybocci, I'm going to close this issue, but if you need further help @Unbr8kable we can re-ope it. |
Hi,
I have a Problem with the Templates.
When I open a new Inicident via the API and I will use a Template with spaces in the name, the API gave me an error back:
{"errors":[{"id":"6c316469-4986-4707-b0c5-9ba98a826c3d","status":400,"title":"Bad Request","detail":"The request cannot be fulfilled due to bad syntax.","meta":{"details":["The format from message is ung\u00fcltig."]}}]}
But when I change the name to a name without spaces, it works.
I have tried several commands i.e. curl, Powershell Invoke-RestMethod, but the same message appears.
Could you help me with the Problem?
I´m using Version 2.3.14.
It would be nice to have the opportunity to use a template when you close or update an Incident.
The text was updated successfully, but these errors were encountered: