Hi Robert On Jun 25, 3:53 pm, Robert Buchholz <[email protected]> wrote:
> On Thursday 24 June 2010, culliard wrote: > > > 1. BacklogDrag& drop seems to work in both Open and Pro - i thought > > it should only work in pro? > > Right.Dragand drop in a backlog works in both Pro and the Open > version. Pro comes with the Whiteboarddragand drop and the backlog > inline editor though ;-) > > > 2. Why is it not possible to grag & drop tasks between user stories? > > I'm a bit curious, why do you want to do this? Unless you add a task to > a story accidently, our tasks are pretty much specific to getting a > certain story done. Sometimes a task gets added to the wrong user story. I guess it would be a 'nice feature' to drag and drop between user stories. Another way to do it would be ability to change user story from within task information dialog from backlog /whiteboard. i have several other tweaks in mind but will create another post for those. > > > Otherwise it is cumbersome to do it > > - go to original user story > > - click edit > > - delete task link > > - go to new user story > > - click edit > > - add task link > > > Will this be available in later version? > > Yes, that's the way to do it. It's often easier to close the old task > and just create a new one if you do not have much metadata on the task. > > > By the way I found an inconsistency (bug?) - I was able to reference > > the same task from 2 user stories (by just doing last 3 steps above). > > Backlog view shows same task under each user story with orange ID and > > small arrow (i suppose to highlight the fact it is referenced twice. > > However the whiteboard only shows the task under new user story. > > You're right -- the multi-link feature is only available in the backlog. > Tasks will be displayed by only one of the stories they are linked to in > the whiteboard. This is a known limitation of the whiteboard, but we > have not planned this feature right now. In my opinion, linking an item > to multiple parents makes most sense in the Story -> Requirement > relation and less sense in Task -> Story. But maybe I'm missing > something. Can you give an example of how you use this for tasks? i happen to come across it while testing. At the moment we don't really use it that way although developers were suggesting they like to track progress of a component or sub module e.g. whole GUI. To do that tasks would need linked to 2 'user stories' - one for delivering value within sprints and other the for component which could cross several sprints or even milestones. I guess its like a component burndown but not sure what value this would give to the team. > > Regards > Robert -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by agile42 GmbH <http://www.agile42.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
