Webhook from jiracloud not working with ssl/let's encrypt

[Pantelis Karamolegkos]

We have set up a webhook from jira cloud to a custom application;

our application is containerized and behind nginx reverse proxy that uses Let's Encrypt certificates;

The webhook seems to work over http but not over https.

nginx logs indicate no specific error;

The webhook also works over https when it is manually triggered from postman;

any suggestions?

[Andy Brook · Accepted solution]

Open Issues means, does the issue have a resolution set, ie, works regardless of workflow.

[Marketa Dvorackova]

Understood, thanks a lot. So if there is a state Resolved followed by Closed, it includes both of them (issue has a resolution set). No chance to make this work only for Closed in the example (meaning: Resolved? ok, comment and reopne, Closed? oh no, don't touch, create a new one).

[Andy Brook]

ANy kind of resolution indicates resolved, which isn't open, it was the simplest way I could think of to achieve the aim. Further options could be achievable, eg a sub-select for commenting on specific resolutions only (if a resolution was set). Log a feature request please ;)

[Marketa Dvorackova]

Thanks, will do:)