Stskeeps, I think it is quite a good idea, however, I would suggest to try to simplify from miniproject to a simple action handling system.

Standard action definition:
- title
- description
- owner
- status
- deadline, priority

We could add contributors, comments, logged history, dependency on other actions and probably remove deadline and priority.

The standard action statuses: draft, open, work in progress, closed, cancelled. That's pretty much what you were writing:
- draft = waiting
- open = boarding
- work in progress = implementation
- closed = completed
- cancelled is for "false alarms", when during implementation it turns out that this action is not needed/not possible.

While it is only a small modification to your proposal, this would give the benefit to be able to use it across bugtracker, brainstorm, council sprints, community championed tasks (or even for self-imposed tasks, like a learning path).

Either way, I think it would be important to implement a solution to the problem you have raised.

( these notes were taken from my maemo.org prezi, which is currently in proposals-devel, usual warning applies: http://prezi.com/qefcq69cpjkm )