Support On Demand Release Evidence
Problem to solve
The general problem of changing evidence (issues, milestones) can be solved simply with on-demand Evidence collection. In this scenario Releases would have many Evidence objects (
- Related Comment: #38103 (comment 277327850)
Suggested approach: on-demand Evidence collection
This issue will implement support for multiple Evidences for a single Release.
An Evidence snapshot may be automatically created, depending on the type of Release. A Release can be created with a historical date, no date or a future date.
- Historical Release (
released_atdate is before current time) - No Evidence is created.
- Immediate Release (no released_at date is provided, Release is created immediately). A single Evidence object is created
- Upcoming Release (
released_atis a future date) - Evidence is created immediately, and a second Evidence object is schedule to be created at the time of Release.
Additionally Evidence can be created "on-demand". An API endpoint will be provided to create Evidence 'now' (via async Sidekiq job). Multiple evidences are displayed on the Release page, along with the collected_at date (same as created_at).
On the UI, multiple items will be displayed under evidence collection, with the timestamp it was collected at, Updated and version tag in the download link.
Permissions and Security
What does success look like, and how can we measure that?
- Release evidence is captured at any point in time by users
What is the type of buyer?