Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sub projects inside projects or nested projects #47

Closed
GoogleCodeExporter opened this issue Apr 30, 2015 · 7 comments
Closed

sub projects inside projects or nested projects #47

GoogleCodeExporter opened this issue Apr 30, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

I think bigger projects are better managed if they are split up into sub 
projects.  This helps 
better management of projects as sometimes we later realise that some actions 
are actually 
projects as they will require more than one action item to complete them. Under 
such 
situation it would be really helpful if actions can be converted into projects, 
or sub projects. 
And these sub projects should shown only under the parent project. 

Original issue reported on code.google.com by prad...@gmail.com on 15 Aug 2009 at 9:32

@GoogleCodeExporter
Copy link
Author

Issue 48 has been merged into this issue.

Original comment by andybry...@gmail.com on 29 Aug 2009 at 12:13

@GoogleCodeExporter
Copy link
Author

Agreed - sub projects are a good idea (along with multiple context)

Original comment by andybry...@gmail.com on 29 Aug 2009 at 12:14

  • Changed title: sub projects inside projects or nested projects
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

I just add "projectname/subproject" as a new project when needed. It's not 
perfect
but at least the name is always visible and it doesn't clutter the interface any
more. Works for me at least. 

Original comment by ribas.en...@gmail.com on 13 Nov 2009 at 1:58

@GoogleCodeExporter
Copy link
Author

Nesting sub-projects are essential for me. I request that this item be 
escalated to a high priority Defect.
It is not intellectually manageable to conceive of large undertakings as a 
linear sequence of Next 
Actions. Like most people - and project managers, and as taught at the Project 
Management Institute 
(http://www.pmi.org) - I formulate projects starting top down (PMI calls this 
the Work Breakdown 
Structure): Start with the big deliverables (e.g., "Get Requirements," "Create 
Acceptance Test," ...), and 
then drill down repeatedly until you have discrete, measurable Next Actions. 
Assign contexts, dates, and 
priorities, and you have the whole picture. Filter to focus. 
Thank you for your consideration.

Original comment by paul.hindes@gmail.com on 12 Dec 2009 at 9:46

@GoogleCodeExporter
Copy link
Author

Original comment by andybry...@gmail.com on 13 Dec 2009 at 9:32

  • Added labels: Size-L

@GoogleCodeExporter
Copy link
Author

Original comment by andybry...@gmail.com on 13 Dec 2009 at 9:53

  • Changed state: Duplicate

@GoogleCodeExporter
Copy link
Author

I reactivate this issue cause I strongly agree with the comments above. 
SubProjects are really missing. So
* converting actions to projects
* assigning parent projects to projects
* creating sup projects
would be very helpful.

(and also the in mentioned 'multiple context')

Thanks a lot

Original comment by cybaerge...@gmail.com on 9 Mar 2011 at 9:37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant