Hi Martin, Thanks for checking, and sorry for the delay in getting back to you.
I re-verified that I'm experiencing the same problem as described even on a fresh install (no modifications or customizations to the Agilo settings). Again, my system configuration is Python 2.5, Trac 0.11.5, Agilo R1918, Genshi 0.5.1. The Agilo configuration looks like the following: [agilo-backlogs] product_backlog.columns = businessvalue:editable, roif, story_priority:editable, rd_points:editable|total_story_points product_backlog.name = Product Backlog sprint_backlog.charts = burndown sprint_backlog.columns = remaining_time:editable|total_remaining_time, owner:editable, drp_resources:editable sprint_backlog.name = Sprint Backlog [agilo-links] allow = requirement-story, story-task, bug-task, bug-story bug.calculate = total_remaining_time=sum:get_outgoing.remaining_time bug.task.copy = owner, sprint bug.task.show = owner, remaining_time cache.related = false cache.timeout = 0 requirement.calculate = total_story_points=sum:get_outgoing.rd_points| type=story,mandatory_story_points=sum:get_outgoing.rd_points| type=story| story_priority=Mandatory,roif=div:businessvalue;mandatory_story_points requirement.story.copy = owner requirement.story.show = rd_points, story_priority story.calculate = total_remaining_time=sum:get_outgoing.remaining_time,estimated_remaining_time=mul:rd_points;get_sprint.get_team_metrics.rt_usp_ratio story.task.copy = owner, sprint story.task.show = owner, remaining_time [agilo-types] bug = owner, sprint, priority bug.alias = Bug requirement = reporter, businessvalue, milestone, keywords requirement.alias = Requirement story = owner, sprint, rd_points, story_priority, keywords story.alias = User Story task = owner, sprint, remaining_time, drp_resources task.alias = Task On Oct 29, 3:29 am, Martin Häcker <[email protected]> wrote: > Hi Clinton, > > > > > > > Steps to reproduce: > > 1. Create a Requirement ticket. > > 2. Go into the 'Edit' tab. > > 3. Click on the "Create a new referenced 'Technical > > Requirement'" (in my installation the story type is aliased to > > 'Technical Requirement'). > > 4. Fill in the ticket and submit. > > > Behaviour: > > 1. Child ticket is created, but the reference link from the parent > > ticket is not created. > > 2. Neither is the link the reverse direction. > > > Expected Behaviour: > > Links in both directions to be created for both the original and > > child tickets. > > > Note: > > * Creating a link from an existing ticket works, i.e. if I type in > > the ticket ID in the Reference # box, and hit 'Create Link' > > I tried to reproduce this in the following way: > * Changed the alias for user stories to read "Technical Requirement" > * Created a new requirement > * Switch to edit screen of the requirement > * Click "Create linked 'Technical Requirement' > * Fill something in & hit create > > For me everything is linked up correctly. > > Could you perhaps verify if this is also happening on a fresh installation? > > Also this might be a configuration issue, so if you could provide the > configuration I could take a look at that. > > HTH, > Martin -- 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
