Redmine

This is just an idea: Would it be useful if a ticket relates to or even can be a subproject?

My consideration is that a ticket could result in a larger task that is worth calling it a project. Since a ticket is part of a project it would rather relate to a subproject. A project provides more functionallity than a ticket. In my opinion and with an abstract view I would say that there should be no difference between a single task (ticket) and a project (also subprojects), besides that a project consist of tasks and subtasks.

Would you like to develop Redmine into this direction so that tasks and (sub)projects get merged? Is this appealing to you? At least it would be nice if there is some sort of connection between a ticket and a subproject. Maybe with some functions, like closing the ticket is only possible if all tickets in the subproject gets closed.