After a job is released - made available - comments and iterations disappear (and asset manager)
M
Melanie Williams
We need to be able to see the historical details of a job - and how it came to it's final iteration. See who asked for a changes (which could later be being challenged), or maybe someone one asked for an amend and it's not been made.
Was a change maybe made to the wrong place - now making the items wrong?
If an approval was done on an earlier iteration - QS/risk ned to be able to see that amends made on a later iteration before being made live - are not material on earlier approvals.
Being able to see the full history of comments and iterations - help with investigation, QS and risk mitigation - particularly in a regulated financial service environment.
Bram Timmers
We acknowledge the importance of seeing a granular (and ultimately: filterable) activity log, that reflects all meaningful events (including the uploading of new iterations, the approvals, and the releases of versions. Introducing those filters is captured in a separate submission on this board, so we're merging these two tickets.