Hello,
I am using automation rules to POST issue data to a webserver. Its working very well but randomly I get an HTTP response 400.
I am assuming the actual data structure of "Issue data (Jira Format)" is changing depending on the ticket data.
Is there anywhere in Jira logs that I can find the actual JSON payload that Jira sent to my endpoint?
I am sorry for the delay on this, I have been out of office on vacation.
Unfortunately I am not aware of any smart variable that can be used to log REQUEST.
I would recommend raising a ticket with atlassian support at https://support.atlassian.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay. That is what I was trying to do.
Thanks for your insights.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
What is the best way to get answers from this community?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Does any one have any insights for me?? I'd be glad to look through documentation, if someone could point me to where it gives the info I need. Thanks!
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.
Hi, pardon. The correct is {{web.response.body}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Eugenio Onofre I am trying to capture the outgoing payload, not the response from the server.
Nonetheless, I tried your recommendation, but I get the same result.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Leslie Martin , would you mind sending a screenshot of the step where you call the API (please hide API details)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Eugenio Onofre ,
Sure, no problem. There are various here in this thread already. I can repost them or take more if they don't tell you what you need.
I am sending a web request to an external server. I would like to log both the post to the server and the response from the server. The response from the server works good with {{webResponse.body}} but I have not had any success with capturing the original payload that gets posted to the server.
I'd really appreciate your input!
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.
I found documentation for logging the web response, but I need to log the web request.
Thanks so much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can have the payload logged as part of your automation. To do so, you can add a log event after the webhook call and log {{web.request.body}}.
Another option would be for you to, inside the webhook automation, test it using the VALIDATION feature.
In case this answer helps you resolve your query, please accept it so it can help other community users in the future.
Regards,
Eugenio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for those insights. It will probably get me to where I'd like to be.
But its not working....
I added a log action to the end of my rule:
But I get this:
I'm struggling to find documentation on what the correct smart values should be? Or is there something else wrong with my rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.