@Richard_Sather - I don’t know if it’s a bug or not, but for Mobile (iOS specifically, unsure about Android), it might be worth pointing out that:
Creating a new subtask within a task with a custom task type causes the new subtask to inherit the parent task’s current custom status instead of defaulting to the first status option of the custom task type.
Example
Suppose you have a custom task with a statuses such as Triage, Backlog, Commit, Working, Completed.
Let’s say you have a parent task with a status of Commit.
When you create a subtask within that parent on mobile, the subtask automatically inherits the status of Ready instead of the first status option of Triage.
Hey @Skyler , well spotted! I can confirm the same behaviour happens in the Android app, which is indeed strange. I’ve gone ahead a broken this out into a separate thread so we can report this as a bug because the desktop behaviour is different (and makes sense).
I’m using custom task types for the items directly under a project. They’re all different stories under a magazine we’re making (the project) and have different statuses: Editing, Fact Checking, etc. But we create tasks under those different stories that I would like to default to standard tasks. Those tasks are things like “Edit this” which don’t need those statuses—they’re either just completed or not. Is there a way to set the default subtask to be standard tasks, rather than custom ones?
