Feature #1840
closed
Merge projects and issues classes to allow more hierarchical project structure
0%
Description
Out company projects have many sub-projects like hardware development/software development/mechanical design/installation/customization. The development process has has many levels of "activities": subprojects, Stages, Tasks, etc.
It would be nice if issues and projects would inherit from only on class/table. And it would be nice if subprojects/tasks could be nested to any depth.
Related issues
Updated by Jeff Dombach over 16 years ago
+1 For subproject nesting to many levels.
Updated by 
Updated by
Updated by Eric Davis over 15 years ago
- Status changed from New to Closed
- Assignee deleted (
Eric Davis) - Resolution set to Wont fix
I don't see any value to the user by merging Projects and Issue to use the same class/table. With #594 subprojects can be nested and #443 will eventually allow issues to be nested also.
Updated by wei han about 10 years ago
user want to merge one project to another. It means one of them is organization A, another is organization B.
when organization A combine with organization B, their issue must be mixed, not delete.
it never means one is sub project.
Updated by Toshi MARUYAMA about 10 years ago
- Related to Feature #5837: Merge Projects added