Nested Incidents/ Service Requests

So what i mean by nested is to add a Parent Child relation to related tickets.

An example is we get a ticket from HR advising that several new associates are being hired we then create a internal Service catalog item per new associate and related it to the original request for tracking it would be nice to show its a child ticket of the former.

It's possible that Runbooks could fix this if we could add more then one Runbook to a Incident and have them run in parallel.

Find more posts tagged with

feature request

Service Catalog

New Feature

incidents

Status: None

Comments

Rich_C

The other scenario where this could be applied is major outage. Other platforms leverage a concept called Major Incident for this purpose. The Parent ticket is 'elevated' and other users who submit incidents for the same issue are then nested underneath it. Ideally the Major Incidents can be reported on separately to better determine how many and how often major incidents occur.