Change Details

It would be all kinds of awesome if we could associate a workboard with a task (and its blocking bugs) rather than requiring the creation of a project. Since tasks are meant to be more easily created and ephemeral than projects, a task with a batch of blocking bugs could be a better match for the concept of "sprints" than a project is. In terms of state management, it would be acceptable (and maybe even desirable) to make sure that the workboard state is locked to a project to prevent an explosion of workboard state to manage. This feature in combination with the concept of sub-workboards (see T78225) would be really nice.