You want to remove some epics from your personal Scrum board, without impacting any other boards. Identify the correct solution.

The board sub-filter is a board-specific JQL query that filters the epics displayed in the Epics panel on a board's backlog view. Because this setting is unique to an individual board's configuration, modifying it provides an isolated way to control which epics are visible. This directly meets the requirement of removing epics from a single personal board without affecting any other boards, even if they share the same main filter. This is the most precise and safest method among the choices provided.

A. Quick filters are temporary, user-activated filters and do not permanently remove items from the board's default configuration for all users of that board.
B. Marking an epic as Done is a change to the issue's data, which would affect its visibility on every board where it appears.
C. Modifying the main board filter is a valid way to remove issues, but it carries the risk of impacting other boards if the JQL filter is shared.
E. Transitioning an epic to an unmapped status is a data-level change to the issue itself, which would impact all boards that display it. ---

1. Atlassian Jira Software Cloud Documentation, "Configure a board": Under the General board settings for Kanban boards, the documentation describes the "Kanban board sub-filter." It states, "This JQL query will filter the epics that appear in the epics panel on the Kanban backlog." This confirms the existence of a board-specific filter for the epics panel, which is the mechanism described in the correct answer. While named for Kanban, this is the only feature listed that provides isolated epic filtering for a single board.

Source: Atlassian. (n.d.). Configure a board. Jira Software Cloud support. Retrieved from the official Atlassian documentation on board configuration. (Section: General configuration > Kanban board sub-filter).

2. Atlassian University, "ACP-610 Managing Jira Projects for Cloud Exam Topics": The exam topics cover board configuration in detail, emphasizing the distinction between settings that are specific to a board (e.g., columns, swimlanes, sub-filters) and configurations that can be shared (e.g., filters, workflows). The ability to configure a board without impacting other projects or boards is a key concept. The sub-filter is a prime example of a board-specific setting that prevents unintended side effects.

Source: Atlassian University. (n.d.). ACP-610 Exam Topics Guide. (Section: Board Configuration and Management).