OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

Enable checkboxes or multi-select in Perses dashboards, ACM Search and right-click actions on resource rows in tree-view.

Why is this important?

We want to enable single place where users can manage their resources, both for single and multiple, in an integrated way and across multiple clusters.

Scenarios

1. As and VM Admin I need to shut down a group of VMs before applying updates to the underlying cluster or node. After the updates are complete, the VMs need to be started again.
2. As a VM owner I review a dashboard showing non-running VMs in the namespaces that I manage that haven’t been used in weeks. Many of them were created for short-term testing and were never cleaned up. This feature will allow me to bulk delete them or create a request in servicenow to delete them.
3. As an Admin I want to tag VMs by project or owner for better visibility. Dozens of VMs need updated labels. 

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)