Skip to content

Log JiraConnect request schema

What does this MR do and why?

Based on the issue's description, we are logging JiraConnect request schema for invalid requests. One error we often see is "invalid request", but we can't tell why the request was invalid because requests are not logged. To learn more about the error, we are introducing logging of the request body.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #379675 (closed)

Merge request reports