moreamazingnick

I got it working by * opening the developer settings in chrome * reload the page * right click on ...login... in network * clear browser cache * clear browser...

I created a pull request for aws-sdk-php which should fix the problem by using the Utils::defaultUserAgent() https://github.com/aws/aws-sdk-php/pull/2780

you can do that using jira automation rules > onchange on icingaStatus -> close but it must be a valid transition in your workflow

what about a macro renderer for the service key (then you can use all kinds of custom vars)? with a fallback for (hostname, servicename and state) to the corresponding arguments...

I thing it would also be a good idea to have this if you have multiple icinga instances opening tickets in one jira project. for example to different (not connected...

do you still need that for ido or have you migrated to icingadb?