Thanks, I noticed the links in the Admin. Just need to set it up so that hierarchy shows. However, when I try to change the information in Links - fields to show in list view and save I get the following error
Trac detected an internal error: IOError: [Errno 13] Keine Berechtigung: '/var/lib/trac/test/conf/ trac.ini' File "/usr/lib/python2.5/site-packages/Trac-0.11.5-py2.5.egg/trac/web/ main.py", line 444, in _dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.5/site-packages/Trac-0.11.5-py2.5.egg/trac/web/ main.py", line 205, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.5/site-packages/Trac-0.11.5-py2.5.egg/trac/ admin/web_ui.py", line 114, in process_request path_info) File "/usr/lib/python2.5/site-packages/binary_agilo-1.1.0_PRO- py2.5.egg/agilo/api/admin.py", line 49, in render_admin_panel return self.detail_save_view(req, cat, page, path_info) File "/usr/lib/python2.5/site-packages/binary_agilo-1.1.0_PRO- py2.5.egg/agilo/ticket/links/admin.py", line 87, in detail_save_view self.links.save() File "/usr/lib/python2.5/site-packages/binary_agilo-1.1.0_PRO- py2.5.egg/agilo/utils/config.py", line 290, in save self.env.config.save() File "/usr/lib/python2.5/site-packages/Trac-0.11.5-py2.5.egg/trac/ config.py", line 201, in save fileobj = open(self.filename, 'w') I am using the Agilo 1.1 appliance. thanks On Oct 16, 1:57 am, [email protected] wrote: > Hi Shikarishambu > > This is how it currently works in agilo. At the top of the hierarchy you have > the requirement, then user story and finally the Task - which is the lowest > level and most detailed piece of work. > > However you can configure the links to include the ability to link bugs with > Tasks and User Stories through the administration section. There is a > configuration area called 'Links'. This is where you can configure the links > and what data is copied over when creating a linked ticket and what > information you want to show on the parent ticket as a summary of the child. > > It's fairly intuitive to set up. If you get stuck, I can give you some > examples. > > Iain > Sent from my BlackBerry® wireless device > > > > -----Original Message----- > From: shikarishambu <[email protected]> > Date: Thu, 15 Oct 2009 19:27:07 > To: Agilo for Scrum<[email protected]> > Subject: [Agilo for Scrum] User Story vs Requirements difference, linking > > Tasks and Bugs to them > > Hi, > How does Agilo differentiate between User story and Requirements? Is > it better to use one over the other? If yes, which one and why? > > Presonally, I prefer to follow this Hierarchy - Rquirements > User > Story > Bugs > Tasks - i.e. Requirements can have user sotries, bugs, > tasks associated to it. > > This brings me to the other question I had - is there a way to link > these in Agilo. > > Thanks- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ Follow Agilo on Twitter: http://twitter.com/agiloforscrum ----- You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
