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.
Photo Viewer
View photos in a modal
Log In
Caroline Ginty
Merged in a post:
Allow different status allocation to original list, when a task is shared with another/multiple lists.
H
Heather M
Currently if I share a task to another list/folder/space that has different status options to the original list the task comes from, it creates the identical status to the list it's been added to. Instead, I would like it to show up in the 'To Do' and for the person overseeing that task in the 'additional list' to be able to operate with different statuses.
EXAMPLE
LIST 1 - This list represents one project/job.
The Statuses for List 1 are 'To Do', 'In Progress' & 'Completed'
The parent task represents one department of the job (ie ordering components) with multiple assignees.
There are several sub-tasks (ie for each individual component to be ordered) with different assignees for each individual sub-task.
There are sub-tasks to the above sub-tasks that then represent each stage of the ordering process (ie. Place order, check & approve proof, confirmation of order received, product received)
I then add this parent task along with all the sub-tasks & sub-sub-tasks to list 2.
LIST 2 - This list represents a department that oversees the ordering of the all the individual components for each job.
The Statuses for List 2 are 'To Do', 'Order Placed', 'Proof Approved', 'Order Acknowledge', 'Product Received' & 'Completed'.
When the task from List 1 arrives from the 'In Progress' status from list 1, it creates a 'In Progress' status in list 2 also, with the task only able to move from 'In Progress' to 'Completed' because these are the options in List 1.
INSTEAD the ordering department would like to be able to move the task through the statuses on it own board, while it remains 'In Progress' in List 1. Once List 1 OR List 2 marks the status as 'Completed' then it is applied to both lists.
At the moment, sharing a task has not benefit to our business.
Caroline Ginty
Merged in a post:
Tasks being added to lists should inherit status of list destination - Need to add tasks on one list to another list with different status
S
Sarah Mizzi
I use click up for product and dev management. I move tasks from my product board to my dev board once they are complete and ready to be developed. Currently I need to duplicate tasks and cannot simply add the task to that list because the status do not change from the first list.
I feel like this is basic product flow and is needed.
Relationships between duplicated tasks also needed along with status view while seeing the relationship. Jira does it and its very common practice.
Caroline Ginty
Merged in a post:
Task on multiple lists with different status
Pascal Sollberger
I have two spaces: One for myself and one with my team. If I get a task assigned I want to add it on my personal board. I recently found the function add to lists but when I use it, it adds the task with the attached status. What I want is to have the task on my board with my status and at the same time on the team board with the status there.
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!
B
Bria Agosto
This would make my life sooooo much easier!
Load More
→