ClickUp Task Reassignment Process
Overview
During ClickUp migrations or space transitions, tasks can lose their assignees due to automation errors or migration artifacts. This article documents the manual workaround for account managers (AMs) to locate and reclaim unassigned tasks until the underlying automation issues are resolved.
This procedure was established during the Sprint 10 Scrum Space migration (March 2026), when a weekend migration caused widespread task unassignment across the new "red" Scrum Space. See [1] for full context.
When to Use This Process
Use this process when:
- Tasks you were assigned to are no longer appearing in your personal task view
- A new Scrum Space or sprint has been created and tasks appear unassigned
- A ClickUp migration has recently occurred and assignees are missing
Step-by-Step Procedure
1. Confirm You Are in the Correct Space
- Verify you are viewing the new/active Scrum Space, not a legacy sprint.
- During the Sprint 10 migration, the new space was color-coded red; the legacy space was green.
- If you are unsure which space is active, ask your team lead or check the sprint planning notes.
2. Search by Client Name
Rather than browsing through all unassigned tasks:
- Use the ClickUp search bar.
- Search by the client name associated with the missing task (e.g., "Doodla", "Didion", "Quora Stone").
- Review the results for tasks that match your expected work.
Why this works: Even when assignees are stripped, tasks retain their client folder associations and naming, making client-name search the most reliable recovery method.
3. Reassign Yourself to the Task
- Open the task from search results.
- Click the Assignee field.
- Select yourself (or the correct team member) as the assignee.
- Confirm the task now appears in your personal task view.
4. Verify Task Metadata
After reassigning, quickly check:
- Due date — Migration bugs have been known to corrupt or reset due dates. Adjust if incorrect.
- Status — Confirm the task is set to the appropriate status (e.g., "In Progress", "To Do").
- Folder/List — Confirm the task lives in the correct client folder and sprint list.
5. Report Anomalies
If you encounter tasks that:
- Cannot be found by client name search
- Appear duplicated
- Have incorrect client names prepended to their titles (e.g.,
[Quora Stone] Project Name)
...escalate to Melissa or Isalia, who are coordinating with ClickUp consultants on the root-cause fixes.
Known Related Bugs (Sprint 10 Migration)
These issues were active as of 2026-03-23 and may recur in future migrations:
| Bug | Description | Status |
|---|---|---|
| Unassigned tasks | Migration stripped assignees from many tasks | Workaround: manual reassignment (this doc) |
| Duplicate projects | Migration created duplicate project entries, likely tied to "virtual consultant" user | In progress — test deletion carefully before bulk removal |
| Broken "Done → Historical" automation | Completed tasks not auto-moving to the Historical list | Workaround: Melissa manually moving tasks; automation credit issue resolved |
| Client name prepended to task titles | Automation incorrectly adding [Client Name] prefix to task titles |
Under investigation |
Roles & Responsibilities
| Role | Responsibility |
|---|---|
| Account Managers (all) | Manually search and reassign their own tasks |
| Melissa Cusumano | Coordinate with consultants; manually move Done → Historical; test duplicate deletion |
| Isalia Ramirez | Assist Melissa with ClickUp cleanup and consultant coordination |
Prevention Notes
- Before any future ClickUp migration, confirm that automation credits are active and sufficient — a credit shortfall was a contributing factor in the Sprint 10 issues.
- After migration, run a spot-check across at least one AM's task view before the full team standup to catch unassignment issues early.
- Avoid bulk-deleting duplicate projects without first testing on a single non-critical project to confirm no data loss occurs.
Related
- [1]
- [2]
- [3]