Feature #1840

Merge projects and issues classes to allow more hierarchical project structure

Added by Sergio Lerner over 13 years ago. Updated about 7 years ago.

Status:ClosedStart date:2008-09-01
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Wont fix


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

Related to Redmine - Feature #5837: Merge Projects Closed 2010-07-08
Duplicates Redmine - Feature #594: Remove limit on subproject nesting Closed 2008-02-03


#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


#3 Updated by nova zz over 12 years ago

  • Assignee set to Eric Davis


#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

Also available in: Atom PDF