The Issues In Progress gadget automatically displays issues with the status "In Progress" that are assigned to the current user viewing the dashboard. It requires no saved filter or additional configuration, making it the best fit for the described scenario.

Field value changed: Can be used if you're targeting the Status field specifically to detect when it changes from Open to Pending.

Issue transitioned: The most direct and reliable trigger for detecting a workflow transition from one status (Open) to another (Pending).

In team-managed projects, field settings for paragraph fields include a toggle to allow or prevent @ mentions. If users can enter text but not @ mention others, it’s likely that the mention functionality is disabled in the field configuration.

Radio Buttons custom field: Ensures users select only one value during issue creation, which can then drive assignment logic.

Automation rule: Can be configured to automatically assign issues based on the selected value in the custom field, enabling dynamic and rule-based assignments.

The Time tracking field is required to allow users to enter the number of days (or time) spent and the remaining estimate on issues. Adding this field to theDesignissue type enables tracking of effort in terms of logged and remaining time.

Versions in a company-managed project are designed to represent project phases with fixed start and end dates, allow tracking of resolved and unresolved issues, and automatically move unresolved issues to the next version. They also support reporting by version, making them the best fit for this use case.

Project permissions: Users need the Schedule Issues and Edit Issues permissions in the project to rank issues.

Filter settings: If the board’s filter doesn’t sort issues by Rank, users won't be able to reorder them. The filter must include ORDER BY Rank ASC for ranking to be enabled.

An automation rule is the best way to automatically assign unresolved issues to Ken at the end of each day. It can be scheduled to run daily, check for unresolved issues, and assign them to a specific user without manual intervention.

A Kanban board with the backlog enabled meets all the requirements: it shows only in-progress issues (via column configuration), provides a separate area to prioritize incoming work (the Kanban backlog), and allows for releasing issues from the Done column (via version management or Kanban releases).

A Sub-task is always tied to its parent issue and cannot exist independently in a sprint. It is automatically included in the same sprint as its parent, ensuring the work is tracked together.

The user condition is checking whether the reporter is in the Executives group, but the rule is triggered when the issue is commented on. To work as intended, the condition should check whether the commenter (i.e., user who triggered the rule) is in the Executives group - not the reporter.

The rule is triggered when an issue is created, and likely includes an action to assign the issue. If the rule previously worked but now fails with errors, and the rule is still enabled, a common cause is that the user executing the rule (Atalie) lost the Assign Issues permission, preventing the assignment action from succeeding.

In a company-managed Kanban project, the board can have multipleIn Progressstatuses from different workflows mapped to the same column. This allows teams to visually group similar types of work even if the statuses come from different issue types or workflows. It provides flexibility without requiring one column per status.