I have the following payload below but it does not allow me to create an alert with the Jira Rest API
422 Client Error: Unprocessable Entity for url: https://api.atlassian.com/jsm/ops/integration/v2/alerts\", \"taskName\": \"Task-42\", \"payload\": {\"message\": \"Message\", \"description\": \"\", \"details\": {}, \"priority\": \"P4\", \"tags\": [], \"source\": \"CustomRiskRuleEngineAlert\", \"alias\": \"\"}
Hi @sammyl
As you know the 422 error (Unprocessable Entity) means that the payload you are sending to the Jira REST API has problem(s), either because some required fields are missing or due to an invalid value.
I see that you have already filled in the required message field. However, I recommend removing the optional parameters instead of leaving them as empty characters. Start by removing all optional fields to test if that creates the alert successfully, and then add the other fields back one at a time.
Turns out Jira gives u a 422 instead of a 401. It wasn't getting the correct authorization code from the header due to my helm files and was returning the 422. It should be corrected as I was looking in the wrong area
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.