The correct option is Epics.

Epics act as a container for related issues and they are designed to show progress and completion of work for that container so you can see totals and completed counts without adding extra reporting or gadgets. You can filter by the epic link to list all member issues and then perform a bulk change on that filtered set so you can edit every issue in the group with minimal effort.

Filters can locate and list issues across multiple projects and they can be used as the basis for bulk operations, but they do not provide a native grouping container that displays aggregate progress and completed counts per group without additional dashboarding or gadgets.

Components are defined at the project level and are not intended to group issues across multiple company managed projects, so they do not meet the cross project grouping requirement.

Boards provide a visual view of issues from one or more projects but they are not a grouping element that creates an issue container with built in aggregated counts and they do not inherently provide a single click bulk edit for a logical group.

Releases or versions are tied to individual projects for tracking shipped work and they are not suitable for grouping issues across multiple company managed projects in the way required by the question.

Full AWS Practitioner Certification Question