Over the weekend prior to the 2026-03-23 standup, the team migrated to a new "red" Scrum Space (Sprint 10) in ClickUp. The migration introduced several critical bugs that disrupted task visibility and workflow automations. This article documents the known issues, their likely causes, and the workarounds in place while the consultant team resolves them.
See also: [1]
Many tasks in the new Sprint 10 space lost their assignee during migration. The ClickUp activity log shows a "virtual consultant" user removing assignees, but does not record who the original assignee was, making automated recovery difficult.
Workaround: Account Managers must manually reassign tasks.
- If a task is missing from your inbox, search by client name (e.g., "Doodla") in the new red Scrum Space.
- Reassign yourself to any tasks you recognize as yours.
The migration created numerous duplicate project entries throughout the new space. Duplicates appear to be linked to the "virtual consultant" user being recorded as the creator during the migration process.
Workaround: Do not delete duplicates until testing confirms it is safe to do so.
- Melissa is testing on her own projects first (e.g., checking whether deleting one "Didion" entry removes the other) to prevent accidental data loss.
- Duplicate cleanup will be handled during Sprint Planning sessions.
Two automations are confirmed broken post-migration:
Completed tasks are not automatically moving to the Historical list as intended.
Likely cause: An automation credit shortage was identified; credits have since been purchased and the follow-up sent to the consultant. Resolution is pending.
Workaround: Melissa will manually move "Done" tasks to the Historical list until the automation is restored.
Note: Sprint 10 also carried over already-completed tasks from prior sprints. These should be monitored to prevent the "Done" list from accumulating indefinitely across sprints.
Some task titles are being incorrectly prefixed with the client folder name in brackets (e.g., [Quora Stone] Project Name). This is an unintended automation behavior pulling from the client folder structure.
Status: Under investigation. No workaround beyond manual title correction at this time.
The "virtual consultant" ClickUp user appears to have been the agent executing the migration. Side effects include:
- Reassigning or removing task assignees
- Creating duplicate project entries attributed to that user
- Triggering or corrupting automation rules
An automation credit shortage may have compounded the issue by preventing some automations from completing correctly during the migration window.
| Issue | Owner | Status |
|---|---|---|
| Unassigned tasks | All AMs (self-service) | In progress — manual reassignment |
| Duplicate projects | Melissa | In progress — testing before bulk delete |
| "Done" → "Historical" automation | Melissa & Isalia + consultants | Pending — manual workaround active |
| Client name prepended to titles | Melissa & Isalia + consultants | Under investigation |
| Missing tasks (e.g., Seamless from Andrzej's view) | Melissa | Under investigation |
| Automation credits | Melissa | Resolved — credits purchased, follow-up sent |
Melissa and Isalia are the primary contacts working with the ClickUp consultants on all automation and structural fixes.
The new "red" Scrum Space (Sprint 10) runs alongside the legacy "green" Scrum Space (Sprint 57). Sprint 10 is intended to be the canonical working space going forward. The two spaces are not directly comparable — Sprint 10 appears to contain more tasks than Sprint 57, partly due to the duplicate issue.
Task folder membership can be inspected by hovering over a task and checking which folders it belongs to (e.g., Account Management + Sprint 10), which is useful for diagnosing misplaced or duplicated items.