Hello Felix,

On 26 oct, 08:02, Felix Schwarz <[email protected]>
wrote:

> That's a really old version so I think no one tested your scenario so far :-)

That's understandable.


> However maybe our upgrade system can update your data automatically. Did
> you try loading your unmodified DB in a trac 0.11 + Agilo 0.9.1
> environment? We should be able to update at least from Agilo 0.6 -> 0.9.
Well, no. I didn't tried that. we immediatly been to version binary-
agilo 1.3.0.3-PRO.


>
> > My problem is that when I select a Sprint backlog only Req, US and Bug
> > are displayed but the Tasks are not.
>
> One thing that came to my mind is linking configuration: Tasks should
> link to no other item. Can you send us the agilo-links section from
> trac.ini?

I check in trac.ini and in the admin/agilo/link page and it looks ok.

[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 = baseestimate, component, priority, version, milestone, sprint
bug.alias = Bug
requirement = cc, businessvalue, milestone, keywords
requirement.alias = Requirement
story = owner, sprint, rd_points, story_priority, keywords
story.alias = User Story
task = drp_resources, baseestimate, remaining_time
task.alias = Task

[agilo-backlogs]
bug_backlog.columns = owner, sprint, total_story_points,
estimated_remaining_time, total_remaining_time
bug_backlog.name = Bug Backlog
product_backlog.columns = businessvalue, roif, story_priority,
rd_points|total_story_points, milestone
product_backlog.name = Product Backlog
release_backlog.columns = total_remaining_time, sprint, reporter,
story_priority, businessvalue, total_story_points,
estimated_remaining_time, owner, rd_points, mandatory_story_points,
status, milestone
release_backlog.name = Release Backlog
sprint_backlog.charts = burndown
sprint_backlog.columns = remaining_time:editable|total_remaining_time,
owner:editable, drp_resources:editable
sprint_backlog.name = Sprint Backlog



>
> I suspect that something in your Agilo config is not 100% right but you
> can try yourself by using Firebug/Web Inspector. Check the JSON that is
> transferred for your backlog (should be the longest/biggest JSON
> request) contains some task data.

That's a good idea. I just checked but found no trace of task. Note
that the reference to the outgoing and incoming links are well given,
but the list just contains req and us.

The list is very big, but I copied the last two item in the json
structure:

    * {
          o status: "new"
          o can_edit: true
          o roif: null
          o description: ""
          o reporter: "meurissr"
          o cc: ""
          o resolution: ""
          o mandatory_story_points: 0
          o businessvalue: "100"
          o time_of_last_change: 1288008494
          o summary: "rmeu test - req"
          o keywords: ""
          o incoming_links: [ ]
          o total_story_points: 0
          o milestone: "3.3.1"
          o owner: ""
          o
            -
            outgoing_links: [
                + 6610
            ]
          o type: "requirement"
          o id: 6609
      }
    *
      -
      {
          o status: "new"
          o
            -
            outgoing_links: [
                + 6611
                + 6614
            ]
          o can_edit: true
          o description: ""
          o reporter: "meurissr"
          o story_priority: "Mandatory"
          o resolution: ""
          o time_of_last_change: 1288012701
          o summary: "rmeu test -us"
          o keywords: ""
          o
            -
            incoming_links: [
                + 6609
            ]
          o estimated_remaining_time: null
          o owner: ""
          o rd_points: "0"
          o sprint: "3.3.1"
          o type: "story"
          o id: 6610
          o total_remaining_time: 12
      }

]


-- 
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

Reply via email to