# May 2020 ### New features * [Stakeholder engagement](/users-and-access-management/user-roles-and-permissions.md): keep stakeholders in the loop during critical alerts. ### New and updated integrations * [AWS Personal Health Dashboard](/integrations/inbound-integrations/aws-phd.md) * [StatusCake](/integrations/inbound-integrations/statuscake.md) * Serverless outbound integrations: * [AWS Lambda](https://github.com/iLert/docs/blob/master/changelog/broken-reference/README.md) * [Google Cloud Functions](https://github.com/iLert/docs/blob/master/changelog/broken-reference/README.md) * [Microsoft Azure Functions](https://github.com/iLert/docs/blob/master/changelog/broken-reference/README.md) * [Icinga v2.x](/integrations/inbound-integrations/icinga.md) (updated): there is a dedicated plugin for Icinga now on our [GitHub repo](https://github.com/iLert/ilert-icinga). You can now override the alert priority from within Icinga and we include the comments that you enter in Icinga when ack’ing a problem in the event log of the alert. * [JIRA](/integrations/inbound-integrations/jira.md) (updated): When you setup a connection from your alert source in ilert to your JIRA instance, projects and issue types are now dynamically fetched from your JIRA instance, so you can select the issue types when ilert syncs an alert to JIRA. You can even include custom fields. * [Webhook](/integrations/outbound-integrations/webhook.md) (updated): you can now fully customize the payload for outbound webhooks. ### Improvements * [API end point](https://api.ilert.com/api-docs/#tag/Uptime-Monitors) for uptime monitors * Uptime monitors: support for milliseconds in check timeout * Flexible periods in repeating on-call schedules: set an arbitrary period length and chose between days and weeks as the period unit ([blog post](https://www.ilert.com/blog/2020-05-27-stakeholder-engagement-release-notes/#flexible-periods)) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ilert.com/changelog/2020/may-2020.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.