Title: Support configurable status groups for action workflows Summary Please add the ability to assign custom action statuses to configurable status groups—such as Active, Completed, Deferred, and Canceled—rather than treating every non-completed status the same. This capability is important for organizations migrating from Wrike and for teams that need more accurate workflow reporting, notifications, and action/task filtering. Problem In Wrike, every custom task status belongs to a primary status group: Active — work is underway or actionable. Completed — work has reached an end state. Deferred — work is postponed and not currently actionable. Canceled — work has been ended or is no longer applicable. These groups affect how tasks behave in default views, notifications, dashboards, overdue reporting, email digests, and search filters. Hive currently does not provide status groups. This creates a workflow gap because end-state statuses do not always mean “completed.” For example, our organization used a Withdrawn status within the Completed group in Wrike. A withdrawn task is not successfully completed, but it is closed and should no longer appear as an active, overdue, or actionable item. Without status grouping, Hive makes it difficult to distinguish between: Tasks that are actively in progress Tasks that were successfully completed Tasks that were withdrawn, canceled, rejected, or otherwise closed Tasks that are intentionally deferred or on hold This affects reporting accuracy, operational visibility, overdue tracking, and migration from Wrike. Requested Enhancement Add a configurable status group field for every custom task status. At minimum, Hive should support these groups: Active: Tasks remain actionable. Included in default task lists, notifications, email digests, and overdue reporting. Completed: Tasks are closed and no longer actionable. Excluded from default to-do notifications, overdue lists, and active-task views. May include statuses such as Completed, Approved, Delivered, or Withdrawn. Deferred: Tasks are paused or postponed but may resume later. Excluded from overdue reporting and active-task notifications by default. May include statuses such as On Hold, Deferred, or Waiting. Canceled: Tasks are permanently closed without completion. Excluded from overdue reporting and active-task notifications by default. May include statuses such as Canceled, Rejected, Duplicate, or No Longer Needed. Key Requirements Administrators should be able to assign each custom task status to one status group. Workspaces should be able to create multiple custom statuses within each group. Default task filters, dashboards, notifications, email digests, and overdue reporting should use status groups—not individual status names—to determine whether a task is actionable. Reports should allow filtering and grouping by both: Individual status Status group The system should preserve distinctions between different closed outcomes. For example: Completed = work was delivered Withdrawn = request was withdrawn before completion Canceled = work was intentionally terminated Existing Hive statuses should remain supported, with a sensible default group assignment. Status-group mappings should be available through imports, exports, integrations, and the API where applicable. Example Workflow Custom Status Status Group Expected Behavior Not Started Active Actionable; included in overdue reporting In Progress Active Actionable; included in notifications Waiting for Review Active Actionable; included in active views On Hold Deferred Not overdue; excluded from to-do notifications Completed Completed Closed; excluded from active views Withdrawn Completed Closed; excluded from active views and overdue reporting Canceled Canceled Closed; excluded from active views and overdue reporting Business Value Configurable status groups would: Enable a more accurate migration path from Wrike. Improve reporting on true completion versus non-completion outcomes. Prevent closed tasks, such as withdrawn requests, from being incorrectly treated as active or overdue. Reduce notification noise and dashboard clutter. Give organizations more flexibility to create workflows that reflect their real operational processes. Make Hive more suitable for teams with complex approval, intake, project, and service-request workflows. Requested Priority We would appreciate this being considered as a product enhancement, particularly for organizations migrating from Wrike or managing workflows with multiple valid task end states.
