Currently, once a release is completed, it is locked and no further changes can be made. In our team, we frequently run dry runs or test executions from tagged templates for POC or feature development purposes. As a result, these non-production runs are included in release metrics and visualisations, which can skew dashboard insights.
It would be beneficial to allow users with appropriate permissions to add or remove tags after a release has completed, mainly for housekeeping and to ensure more accurate reporting.
by: YINFENG X. | 4 days ago | Templates & Releases
Comments
Thank you for the suggestion. To better understand the use case, we have a few questions:
1/ When you run a dry-run or test execution, is there a reason the release cannot be tagged before it starts, or does the need to add a tag come up only after the run completes?
2/ How are you using reporting today where these releases cause issues? For example, are you filtering or excluding releases by tag in the Release dashboards, or exporting data for use in an external tool?
3/ Do you need to keep these dry-run releases in the system after they complete, or would deleting them after review be an option?
4/ How often does this happen - is it occasional testing or a regular part of your team's workflow?