Maybe there is a better way to do this, however this so far looks good.
In Advanced Roadmaps, I've defined a model/template of Initiatives (top) to sub-task (bottom) of the work we require for a release. (The Initiative represents the Release name, one Epic for each of the teams participating in the Release, a Task representing a single group of activities for the release, and subtasks for individual deliverables broken down when possible to work that can be done in a couple hours).
Subtasks (and tasks) get linked together indicating basic progression of work (dependancies). All good so far.
It would be *outstanding* if there was some way to even come close to this:
With the issues defined and dependencies mapped, could for each issue I set a number, indicating the number of days the issue is expected to take?
Then, I set the start date of the very first issue and it builds a picture and I know when it will be done, OR - and this is where it would be cool) I set the finish date for the last issue and it reverse build the picture and I know when to start.
That ultimately is what I seek to do.
This appears to be related to your earlier post here, where I offered a suggestion:
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.