Quote:
|
Originally Posted by HiramNetherlands
I'd like to see task aliases (in another thread called 'cloned tasks'), i.e. tasks that are part of more than one project.
|
I certainly see how cloned actions would be useful, but they have all sorts of UI ramifications that would introduce a bunch of new work. (For example, an action can be "available" in one project and "not available" due to dependencies in another, so which one is right? In context view, do we list each clone of the action separately, or do we modify the project column to somehow handle multiple project assignments?)
So we won't be doing cloned actions for 1.0, though we'll certainly consider them for future releases.