> This is a known issue, Trac has no foreign key in place, ... any other idea?
I'm not sure how Trac itself handles it, but when renaming a
milestone, Trac does update the tickets table with the new milestone
names. So some where in Trac it's able to notice that it's changing
one and should update the other table. (And yeah, sadly there's no
milestone_id in Trac.)
> Right, unless you didn't check the "Strict" option in the Backlog
> Admin... in which case would be right, you will load also all the
> ticket of the selected types which are not explicitly planned for
> other milestones...
Sadly, that's not true. It's including lots of tickets that already
have other milestones. Because those tickets with milestones don't
have sprints! A requirement won't have a sprint, which causes it to
get selected, even if it has no links to any other tickets, and
doesn't belong to the current milestone. So I really do think this SQL
needs to have the "in ('')" removed when there are no sprints. The act
of so drastically changing what is seen by the absence of a sprint
against the milestone is very confusing and non-intuitive. (Without a
sprint on the milestone I get 160 tickets, with a sprint in the
milestone, I get 2.) So not only would I say the idea that a milestone
report should show non-milestone tickets just because there's no
sprint is a bad idea fundamentally, it's also just plain broken as
that's not what the query does.
--
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
