(Services and Service Request) for a few years.
I think that Services would benefit from an optional "service_parent" field, so
that a hierarchy could be created. Items at the top level could be set at "0"
and then items underneath would use the service_code of their parent.
This would enable a hierarchy to be created rather than one flat list, which
can be hard to use if integrated into a front-end and there are many entries in
I'm keen to get others' views on this and to ask, if there's consensus that
this would be an improvement, how do we add this to the spec.