> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/changelog/2026/june-2026.md). # June 2026 ### New features and improvements * We have launched a new mobile app update that adds full support for the new incident management features * Postmortems can now be generated and linked directly from the new incident management * We have finished the migration of our reports backend to our new inhouse bigdata stack * We added **escalation policy and priority overrides to the call flow `CREATE_ALERT` node** ### Integration updates * We have introduced new inbound integrations: **Zoho Help Desk** and **Oracle Enterprise Manager** * We re-enabled the **AWS EventBridge** integration * We added **templating for event link titles**, letting you customize the labels of links extracted from inbound payloads * We enabled **templates for Kibana** alert sources * The **Zammad** integration now raises an alert when an ACCEPT event arrives for an unknown ticket, instead of dropping it --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ilert.com/changelog/2026/june-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.