Quang can transition issues from Resolved to Done using the workflow button on issues in his project. However, he cannot drag then from Resolved to Done on the project's Kanban board Identify a possible reason why.

The ability to drag and drop an issue on a Kanban board is dependent on the board's column configuration. Each column on the board represents one or more workflow statuses. If the 'Resolved' and 'Done' statuses are both mapped to the same column, there is no separate column to drag the issue to. Therefore, the drag-and-drop action for that specific transition is not possible on the board. Since Quang can perform the transition from the issue view, it confirms he has the necessary permissions and the workflow is valid. The limitation is purely a result of the board's visual layout.

A. Quang lacks a project permission. This is incorrect because Quang can successfully transition the issue using the workflow button on the issue view, which confirms he has the required 'Transition Issues' permission.
B. Quang is not a board administrator. This is incorrect because board administrator privileges are for configuring the board's settings, not for performing standard issue transitions like moving cards.
D. The board has a sub-filter configured. This is incorrect because a board's sub-filter (or Quick Filter) only restricts which issues are displayed on the board; it does not prevent valid transitions for the issues that are visible.

1. Atlassian Jira Software Cloud Documentation, "Configure columns": This document explains how board columns are configured by mapping workflow statuses to them. It states, "A column represents a status in your team's process... You can also add multiple statuses to a single column." This directly supports the premise that 'Resolved' and 'Done' could be in the same column, making a drag-and-drop transition between them impossible. (Reference: Atlassian, Configure columns, "Map statuses to columns" section).

2. Atlassian Jira Knowledge Base, "Unable to transition an issue by drag and drop in Jira Software boards": This official support article lists potential causes for this exact problem. The primary cause listed is: "The initial and final statuses of the transition are mapped to the same column of the board." This directly validates that option C is the correct reason for the described behavior. (Reference: Atlassian Knowledge Base, Article ID: KB0024911, "Cause" section).