Y24-064 Develop an audit mechanism for retention instructions that can later be displayed in the UI

[dasunpubudumal]

User story As a developer, I need to create an audit trail for retention instructions stored in labware table. Please refer to https://github.com/sanger/sequencescape/issues/4093 to see how retention instructions are stored in the table.

• [ ] Establish an eventful has_one relationship between labware and events table. See how a similar implementation in lib/eventful_record.rb:29.
• [ ] When persisting a retention instruction (i.e., when uploading a manifest), store an event in the events table in the database. This can be done by updating the lib/eventful_record.rb module.
• [ ] Update the codebase to persist another record to the events table when an update (or a deletion) is made to the retention instructions of a particular labware.

Who are the primary contacts for this story Dasun, Katy

Who is the nominated tester for UAT

Acceptance criteria To be considered successful the solution must allow the following:

• [ ] To persist and audit record in the events table when a create, update or a deletion is made for a retention instruction of particular labware.
• [ ] Update: Populating the events table with correct eventful_id should bring in the data related to the labware history in Events History page.

Dependencies This story is blocked by the following dependencies:

• https://github.com/sanger/sequencescape/issues/4093

References This story has a non-blocking relationship with:

• https://github.com/sanger/sequencescape/issues/4003

Additional context Add any other context or screenshots about the feature request here.