Log edits without showing username/timestamp

Yeah this is really hard to describe. Correct, the Reshoot table is a child of the Shots table.

What is happening is this, as an example:

1. In the Shots table I have a ShotID called  1306426_alternate1.tif which has a JobID of  06072017_NYS5_UNREC_W_1806.
2. If this ShotID has the JobID modified I want two new records in Reshoot created.
   A record of the ShotID (1306426_alternate1.tif) and the old JobID (06072017_NYS5_UNREC_W_1806)
   A second new record of the ShotID and it's new, modified JobID ( 12242017_NYS5_UNREC_W_1806).
3. I can do this pretty easily with an Action. This leaves me with 2 new records in Rehoot for this ShotID because it's been shot twice. Perfect.
4. Here's the problem: If this ShotID is modified again, the Action is going to add two new records again. It will add a record for what is now the the old JobID ( 12242017_NYS5_UNREC_W_1806) and another for the new JobID ( 02022018_NYS5_UNREC_W_1806).
   Problem is, what is now considered the old JobID (12242017_NYS5_UNREC_W_1806) has already been added once before when it was considered the new JobID.
   
   

Basically I want 2 records created upon the first modification of JobID (to log the original JobID and the new one) and then every subsequent modification should only get one new record created (the new, modified JobID). If I leave the Action as it is now, the JobID's start to overlap.

06072017_NYS5_UNREC_W_1806 (original)
12242017_NYS5_UNREC_W_1806 (new)
12242017_NYS5_UNREC_W_1806 (now considered "old")
02022018_NYS5_UNREC_W_1806 (new)
02022018_NYS5_UNREC_W_1806 (now considered "old")
07122018_NYS5_UNREC_W_1806 (new)

This is not something I have been able to work out. I've tried to add the JobID's to a ShotID as new fields instead of entirely new records but that doesn't really work either. The bottom line is, how do I handle that a JobID can be considered old and new at different times?

It's so confusing. If anyone is able to make sense of this you're my hero.