Project

General

Profile

Actions

Feature #1840

closed

Merge projects and issues classes to allow more hierarchical project structure

Added by Sergio Lerner over 15 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Projects
Target version:
-
Start date:
2008-09-01
Due date:
% Done:

0%

Estimated time:
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

Related to Redmine - Feature #5837: Merge ProjectsClosed2010-07-08

Actions
Is duplicate of Redmine - Feature #594: Remove limit on subproject nestingClosedJean-Philippe Lang2008-02-03

Actions
Actions #1

Updated by Jeff Dombach over 15 years ago

+1 For subproject nesting to many levels.

Actions #2

Updated by J Cayetano Delgado about 15 years ago

+1

Actions #3

Updated by nova zz over 14 years ago

  • Assignee set to Eric Davis

+1

Actions #4

Updated by Eric Davis over 14 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.

Actions #5

Updated by wei han almost 9 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.

Actions #6

Updated by Toshi MARUYAMA almost 9 years ago

Actions

Also available in: Atom PDF