We have started using the affected services field. In adding our services, we have too many so would like to work on a hierarchy and dependency structure and there seems to be some built in features but not ideal so looking for others experience and guidance before diving in deeply.
If we have ERP as a service, there is related physical infrastructure (Server, network, building etc) and there is also related services such as the backup service or related by integration (API) such as BI, extranets, CRM, etc. I would love to leverage the affected services ability for similar incidents or change management conflicts. The challenge is we have already 100 + affected services and have many more to enter at this level of granularity. If we get too granular then its too easy pick the wrong service and if we are too general then we can get easily get blocked.
A more specific example is for network service we have almost everything in that location dependant on it if we list it as general meaning it includes internet, wifi, switches, firewall etc. Many of the items are not dependant though as for example wifi can be down and network up or physical network can be down in one part of a building but not in other areas or other buildings etc.
So any advice, thoughts for built in with Jira Assets? I would like to first explore what can be done with existing software or perhaps with a small add on app before exploring other software which I know exist out there.
Thanks in adance,
Lorne
