#1425
- Created on2013-05-14 14:06
- Reported by
- StatusMigrated
- PriorityNormal (3)
- Assigned to-
- Milestone
- Plan Level-
- Due Date-
Make projects depend on actions/projects
I really enjoy how actions may depend on other actions. However, there are situations where projects may depend on actions (or even projects). In my opinion this corresponds to the idea that any action might evolve into a project at any time (Tracks supports that, yeah!), so dependencies should not only be a-a, but also a-p, p-a, p-p.
Leave a comment
on 2013-07-17 08:49 *
By carsten.otto
I feel the need to clarify the need for this feature more, as I experienced many situations in the past few weeks where I'd love to make use of it.
For example, I am currently looking for a job. There are projects to create the CV, for the job application, for individual companies, for general questions, for finance issues, for moving issues, ...
Based on these projects I have a lot of actions (or even projects) that depend on completion of whole projects. For example, the project of moving depends on getting a job first. Some financial issues also depend on getting a job. The "get a job" project depends on the projects for the individual companies. Before sending an application to some company I need to finish the CV project. This example only covers a (big) part of my whole setup, but I have seen similar issues a lot in other aspects of my life, too.
All in all, I do not see any reason why there should be a difference between projects and actions (regarding dependencies).
I'd really love to help on this issue starting in 2014, if I find the time after my day job. Is there any other way how I can accelerate development?
For example, I am currently looking for a job. There are projects to create the CV, for the job application, for individual companies, for general questions, for finance issues, for moving issues, ...
Based on these projects I have a lot of actions (or even projects) that depend on completion of whole projects. For example, the project of moving depends on getting a job first. Some financial issues also depend on getting a job. The "get a job" project depends on the projects for the individual companies. Before sending an application to some company I need to finish the CV project. This example only covers a (big) part of my whole setup, but I have seen similar issues a lot in other aspects of my life, too.
All in all, I do not see any reason why there should be a difference between projects and actions (regarding dependencies).
I'd really love to help on this issue starting in 2014, if I find the time after my day job. Is there any other way how I can accelerate development?
Migrated to GitHub issue #1425