Rob, tying the two statuses together would indeed run counter to Launchpad's conceptual design. Setting the priority and status by default does not, particularly if the person creating the task has permission to do so. This is true regardless of whether the new task crosses project boundaries.
I've tried to update the description to be more problem focused. It's hard to do this for convenience bugs.
Rob, tying the two statuses together would indeed run counter to Launchpad's conceptual design. Setting the priority and status by default does not, particularly if the person creating the task has permission to do so. This is true regardless of whether the new task crosses project boundaries.
I've tried to update the description to be more problem focused. It's hard to do this for convenience bugs.