Incidents, changes and problems — with a status page

Switch on ITSM per project and Iskue adds incidents, changes, problems and post-incident reviews as ticket types with their own fields, workflows and behaviour. They stay ordinary tickets, so TQL, boards, automation and permissions work exactly as everywhere else — and a public status page tells your users what is going on.

What you get

• Incidents that write their own story — Urgency × Impact sets the priority through a matrix, status changes and #timeline comments build a timeline, and stakeholders get updates apart from the working thread.
• Alert intake — monitoring tools post to a secret-protected endpoint; a new alert opens an incident and repeats annotate it instead of duplicating it.
• Changes with guard-rails — risk raised automatically, freeze and maintenance windows on a change calendar, a freeze gate on "Start implementing" and a change-gate endpoint your pipeline can ask.
• Problems and PIRs — create a problem from an incident with the affected services carried over, and a post-incident review prefilled with the timeline.
• Services and assets — a service catalogue with tiers, owners and dependencies, affectedService in TQL, and assets-lite: asset tickets referenced from incidents and changes.
• Public status page — operational, degraded or major outage per service with a 30-day history — only service names, incident titles and stakeholder updates are ever shown.
• Playbooks and entitlements — step-by-step playbooks run on a ticket or on a trigger; products and entitlements per customer or organization, searchable in TQL.