| • Mattias_Ostmar-WMSE | |
| Jan 5 2017, 11:09 AM |
After a batchupload the 'in process' column is filled with non-actionable tasks and the real tasks they refer to doesn't easily get an overview. Unnessecary frustration and cognitive burden
Typical example is T144356 that involves many many more concrete sub-tasks. Should it be a Story? A Milestone? Etc.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | None | T144374 Write/improve learning pattern about batch uploads after the SMVK-Mexiko batch upload | |||
| Resolved | Jopparn | T155739 Create employee/developer onboarding process document | |||
| Declined | None | T154470 Streamline process for batch uploads | |||
| Declined | None | T139335 Finalize document about tasks and subtasks involved in a COH batch upload project | |||
| Duplicate | None | T154655 Replace 'placeholder-tasks' like Handle any maintanence errors... with tasks like Error with accession number |
Maybe the placeholder tasks should be Milestones and the batchuploads should be Projects?
After discussions with Sebastian: the main problem of tasks cluttering the to-do view is solved by not claiming the "place-holder tasks" (stories?), but claim the sub-tasks.
Still not sure how to avoid tasks to linger for months and months in the backlog or in progress