Document additional needs from Release Evidence JTBDs

Problem

When a compliance check is run and the compliance team wants to confirm we have records of production I want to be able to minimize the disruption to the internal teams by empowering the compliance team to self-serve these changes without giving access to the source code so I can adequately respond to an audit

The Release Evidence JTBD above was recently removed because it was mostly a duplication of another JTBD.

However, there are two aspects of the original text that are not covered in the remaining JTBD, and this issue captures the intent to document both needs that were removed from the original JTBD:

• Minimize disruption to internal teams on audit requests
• Enabling self-serve to the compliance team when conducting audits

This could either be done as issues detailing these as user stories, or documenting a new JTBD focused on these aspects.

See !90605 (comment 682482647) for more context.