Loading Profile...
I would like to see releases as containers rather than milestones
We were doing some extended planning yesterday, and it is very hard to use releases as they currently exist. It would be more helpful if the release pane allowed you to attach stories/bugs/chores directly to a release rather than having it rearrange the near the release milestone. There are times when we may have a couple of releases in process at the same time, then it's impossible to tell at a glance which stories are for which release, or how close we are to achieving a release. One of the nice features of lighthouseapp.com is the ability to see a graph of how much work has yet to be done for a release. (if there are 20 points assigned to a release, 15 are done, you are 75% complete). Bugs & chores could get a default 1 point for graphing purposes. The releases could still float in the iteration cycle as they do now, but they would be attached at the bottom of the latest bug/chore/feature in the backlog. That would be a cool feature.
I’m looking forward to getting this feature :)
58
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
-
Inappropriate?One of the next big Tracker features that we are considering is "Story Groups". Story groups could be used to manage feature sets, releases, etc. More to come on this in the next couple of months.
2 people think
this is one of the best points
-
Inappropriate?Mark,
That would be really nice, especially if you provide the ability to convert an existing story into a new story group. That would make for a very intuitive process to split stories into sub-pieces. -
Inappropriate?Anything new on this? Can't figure out how to use the release feature in a useful way. How can I see what's left to do in a release, and what has been done for the release?
1 Comment Add a comment
This is one of the best points
-
As they stand: Any task before the release is part of the release. Nothing special; a done task is done and not-done ones aren't. -
Inappropriate?Optionally stories should belong to a release, so that a release's dependent stories cannot be moved to an iteration later than the release.
This reply was created from a merged topic originally titled
Story belongs to Release.
I’m happy
-
Inappropriate?I tend to have multiple Arcs of development active at a particular time, which I need to track separately and together. I'd like to pin all of these to a Release (typically without a release date), and monitor the stories as a group. Stories in the icebox need not be pinned for my needs, since I only need to group those I'm working on soon.
The UI need only change to support selecting the active Arc/Release, and then hide all other stories.
This reply was created from a merged topic originally titled
Pin stories to a release/group.
I’m waiting
-
Inappropriate?Implement a way to set dpendence between stories to group arround to one release, in order to be able to close it (the release) only if the stories are accepted (finished).
This reply was created from a merged topic originally titled
Releases with Stories Dependence.
I’m thankful
EMPLOYEE
