Use WARN logging level for rejected Jira issue keys

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

We are logging responses of the JiraConnect::SyncService as ERROR if the response contains error messages and otherwise as INFO.

In addition to this, we can log WARN messages when the Jira response contains rejected entities or unknown issue keys. Find more details in this comment: #352411 (comment 869287405)

First thing to note is that you can't count on HTTP status for good logging behavior. 😞 Maybe we can use these structures to log appropriately (I don't know your logging conventions but assuming common levels). Send acceptedBuilds to DEBUG, rejectedBuilds to WARN, and errorMessages to ERROR.

Second thing to note is that none of those cause "errorMessages":["Unknown error"]. I'm pretty sure that's an error in between back-end Jira systems. I'll work with the appropriate team to learn more what these messages mean and how to handle these conditions.