Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Bug #730 (new)

Opened 11 years ago

Last modified 6 years ago

Roadmap tickets counting not consistent

Reported by: andreat Owned by:
Milestone: n.a. Sprint: n.a.
Impact: Minimal Complexity: n.a.
Total Remaining Time: n.a.


The Roadmap ticket counts only the ticket explicitly planned for the Roadmap, the actual rule to synchronize the Sprint and Milestone works, as far as there is one of the two sets. In the Sprint Backlog though all the tasks associated to a Story with a set sprint are appearing also if they do not have a specific sprint set. This is partially solved if the create referenced task is setting the sprint automatically, but if not, the tasks are appearing in the Sprint Backlog only, and the number for the Release percentage in the Roadmap are not trustable.

We need to decide what to show there... and for me the best would be to calculate the Requirements that the Product Owner wish to have for the end of the Release... than add all the stories, and track stories and requirements completion. The tasks do not make any sense in the Release Completion.

Change History (2)

comment:1 Changed 10 years ago by fschwarz

  • Impact set to Minimal

comment:2 Changed 6 years ago by stefano

see related ticket #903

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.15 © 2008-2016 Agilo Software all rights reserved (this page was served in: 0.142330 sec.)