Different statuses for a task that is in multiple lists
S
Shimon Eidelman
When I add a task to another list, I want the the same task would be with different status in each list. you can see reference from Asana.
Log In
Caroline Ginty
Merged in a post:
Workflow Parity: Status Mapping for Tasks in Multiple Lists.
I
Irtiza Batool
Problem Statement: The current "Tasks in Multiple Lists" feature functions as a visual shortcut rather than a true multi-home solution. When a task is added to a secondary list (e.g., from a Backlog to a Sprint), it remains tethered to the Source List’s status workflow.
This creates a "broken" experience for Project Managers because:
- Group Fragmentation: Backlog tasks appear in a separate, disconnected status group within the Sprint view.
- Workflow Misalignment: I cannot move a Backlog item through Sprint-specific statuses (like "Ready for QA" or "Deployed") without permanently altering the master Backlog's structure.
-The "Orphan" Dilemma: To get proper status functionality, I am forced to "Move" the task, which orphans it from the master Backlog and destroys long-term traceability.
Proposed Solution: Local Status Mapping (Virtual Aliasing) I am requesting Workflow Parity across all list locations. ClickUp should allow a task to adopt a "Local Status" that is native to the list currently being viewed.
- Status Inheritance: When a task is added to a secondary list, it should automatically map to that list’s available statuses.
- Virtual Mapping: Allow users to define how a "Backlog" status (Source) maps to a "Sprint" status (Destination). For example, Status: Active in the Backlog could be displayed and managed as Status: In Progress within the Sprint.
- Unified Grouping: Tasks from multiple sources should be visually grouped together under the destination list’s status headers, not siloed into "Tasks from other lists" sections.
- The Business Impact: Without this, Tasks In Multiple Lists is essentially a "read-only" reference tool. Implementing true Workflow Parity would allow ClickUp to support complex Agile environments where tasks must live in a permanent "Master Registry" (Backlog) while participating in active, status-specific "Execution Cycles" (Sprints).
H
Haeyoung Lee
+1 The ability to map statuses across lists so a task can live in both without cluttering views or forcing one team's statuses on the other would be a huge win for cross-functional collaboration
w
wyvern rostu
Please add this feature! This would be incredibly useful for workflows where a single task is relevant to multiple teams or projects but is at different stages in each context. Ideally, there would be an option to choose which properties (like status, assignees, due dates, etc.) are shared or unique per list.
M
Michel Žalac
ClickUp can we please have this feature, its a must-have for our operations. It's essential! From the comments I read this request is pending for more than 4 years now. Please LISTEN to you customers; Tasks Types should have their own independent statuses (like other PM tools have) ...
The current work-around solution that ClickUp is offering of The 'Task-In-Multiple-List' + 'Custom-Field' as 'solution' that ClickUp is offering is not an option; its just the same task with the same status in another list --- you don't need another list for that, you can just have the 'Custom Field'!
Another work-around that does work, but which is not ideal as you're not using one of ClickUp's main features, is described here:
O
Ollie Barnes
This feature would be a huge help to our backlog and sprint management methods - improving visibility greatly across teams, showing exactly where a task is up to :)
Shaun Dobson
We also really need this feature along with everyone else here - please consider it!
Denis Zeziukin
The lack of this feature makes things messy and complicated. It's crazy that this topic has existed for four years and hasn't been solved. I'm even considering moving back to Asana.
Laura Buker
Pleeeease. And while we are on it, keep custom fields info specific to the list you are looking at- maybe give the option to make custom fields visible if selected but not make ALL custom fields visible mandatory. If I add a task to 3 lists, this tasks may have a million customs fields. It's confussing.
A
Alex McGlothlin
I don't understand how this is not a thing yet. This is essential functionality for a task to persist across multiple teams & department. We are trying to get our Customer/Technical support team to use ClickUp alongside developers and they have a completely different workflow.
As development lead, I already have two separate workflows with different statuses I need tasks to go through (Story Planning/custom & Development Work/kanban ) each with different statuses. Our customer support team on has a completely different workflow which needs to integrate with that. Their workflow is more like "ticket intake -> send to developers for story planning -> developers do the work -> we review the work and respond to the customer -> customer signs off."
Without having different statuses across different lists our customer support team is not able to see WHERE in our planning or work-cycle a task is!
I've been singing the praises of ClickUp for years, but the lack of this feature may very well be a deal-breaker. I hope this gets prioritized and added in soon!
L
Lucas Seymour
This is essential!
Load More
→