Interrelated IDs (incidents and CRs)

[Rogfrich]

Thanks all.

@johnnydecimal

In this scenario, where cough you’re using ServiceNow or similar, you’ve already got an ID. INC or CR or whatever. I’d caution against creating another ID which usurps that

Yep, that makes sense. I was thinking of an ID AC.XX representing “a collection of incidents I’m working / have worked on” with individual INC reference numbers collected under that single ID. - and another AC.YY representing “a collection of CRs I’m working / have worked on” with individual CR reference numbers collected under that single ID.

I see these as broadly transactional, following the creative pattern.

@johnnydecimal

There’s also a very clear data model already (ITIL). Again, don’t re-invent that.

I think maybe I wasn’t clear. My JD system isn’t going to form any sort of official record (my system will only be used by me). The canonical record of the incident will be in the service management tool, with all the structured data you’d expect.

@johnnydecimal

I guess the question is, what are you trying to achieve? What’s the purpose of you recording incident & change IDs? (Not saying there isn’t a valid reason. We just need to understand what it is.)

This is about me keeping track of my thoughts, scribbles, ideas relating to each incident and CR. I need somewhere to keep that stuff in JD, and this seems like a reasonable way to do it:

• a single ID for incidents straddling a “folder” per incident, named by INC ref
• a single ID for CRs straddling a “folder” per CR, named by CR

That way I’m not using a whole ID for what might be quite a small thing.

My question was really around managing the fact that the linkage between incidents and CRs can be complex.