Removing a Deployment Report Activity
- Dominant language
- No language data
- Stars
- 20
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Note that this is not expected to be an issue for us for this submission because we expect to only be adding data, but I wanted to raise it for more discussion at a later time (unless there is already a way to do this.)
How can we remove the deployment report for a specific activity for an investment? In other issues that have been brought up, it appears that "reportsReleases" is not a supported field, so I assume setting that to "No" would not clear the existing data (and - presumably because it is not supported - reporting "No" currently still requires also answering other questions.) Similarly, "delete" was indicated as not supported for the deployment report itself (as deletes happen via the business case/SIR), and, in any event, that would be problematic long-term as it might result in old data for completed projects being lost. I am also assuming that an "update" does not completely overwrite the set of activities with what is provided.
This may come up because the deployment report is optional for some activities and so there may be times where the agency wants to remove optional data that was innaccurate, supplied in error, or no longer applies. This includes cases where a parent activity was split or more work was added and the parent is now a child activity.
I think this is where support for "reportsReleases" as an optional field might make sense (and perhaps it still works this way, though it doesn't appear to.) Ideally, if set to "No", it would not require any additional fields and would clear out any data previously provided. If omitted, left blank, or set to "Yes", then the normal, existing rules would apply. An alternative would be to introduce an activity status field, though I do like the flexibility of not having to designate add vs. update when that can be determined on the database side.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.