Hi Steve, Am 14.01.11 21:31, schrieb Steve S: > References, unless I'm using them incorrectly, don't really seem to do > very much other than provide a text field that isn't linked to > anything. I have tried referencing other tickets by number, both with > and without the number sign. I would definitely appreciate "stronger" > linking in this regard.
If you want this linking information in it's own field, you can set it's type to wiki and then just use the normal trac-wiki-link syntax in there <http://trac.edgewall.org/wiki/TracLinks> However often it may suffice to just put those links inside the description of a ticket so others can easily click them. > However, the biggest problem that I see with > your approach is that you aren't always going to be able to foresee your > tasks in great enough detail to be able to make stories specific enough > before you begin your tasks. Being able to break down a task into > subtasks whenever you you deem it necessary would be a hugely useful > feature. Perhaps polling the community would be a good idea on this, if > the Agilo team wouldn't be opposed to implementing something like this. Could you please provide some examples of problems you encounter in doing this? We have found that in combination with estimation of stories and then breaking down stories into smaller ones in preparation for planning works quite well for this. Of course this requires some lookahead as a bit of the backlog will need to be estimated in lookahead sessions by the team. One other thing: We frequently break down tasks into smaller ones if we attack them, usually by just doing it and then deleting the task that was previously encompassing them. Do you have any requirement that makes this workflow work badly for you? Regards, Martin -- 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 Agilo Software GmbH <http://www.agiloforscrum.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
