Feature #1840
Merge projects and issues classes to allow more hierarchical project structure
| Status: | Closed | Start date: | 2008-09-01 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Projects | |||
| Target version: | - | |||
| Resolution: | Wont fix |
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
History
#1
Updated by Jeff Dombach over 13 years ago
+1 For subproject nesting to many levels.
#2
Updated by J Cayetano Delgado over 13 years ago
+1
Updated by #4
Updated by Eric Davis over 12 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.
#5
Updated by wei han about 7 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.
#6
Updated by Toshi MARUYAMA almost 7 years ago
- Related to Feature #5837: Merge Projects added