#10130 closed defect (worksforme)
Roadmap milestones show 0% completion after update 0.12.1 -> 0.12.2
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | roadmap | Version: | 0.12.2 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
I just noticed that all our milestones show 0% completion.
The progress bars are OK its only the number which says 0%.
Honestly I noticed it today, but we did the update 2 days ago, and since a human being (at least me) looks more on the progress bars, it could be that this was wrong before.
Anyway: could you give me some hint?
What could I look for, or how can I check this? (and repair ;-) )
Stephane
Attachments (0)
Change History (12)
comment:1 by , 14 years ago
Keywords: | needinfo added |
---|
follow-up: 3 comment:2 by , 14 years ago
Description: | modified (diff) |
---|
(French speaking person, right? ;-) )
comment:3 by , 14 years ago
Replying to cboos:
(French speaking person, right? ;-) )
yes ;-)
and yes we use [milestone-groups], since we use the test workflow similar as describe in: TracWorkflow#Example:AddingoptionalTestingwithWorkflow
so our testing tickes are highlighted in yellow.
Stephane
comment:4 by , 14 years ago
Priority: | normal → high |
---|
OK I did a test:
- I look at my trac 0.12.2 and see in the roadmap a completion of 0% for all milestones
- I get Trac-0.12.1.tar.gz, and install it.
- I look again in the roadmap and see the correct % values in the milestones.
I didn't change nothing else!
Could you give me a hint on where I could look for this:
- where are the % completion values calculated
- can I activate some log somewhere
Thanks :-)
Stephane
comment:5 by , 14 years ago
By the way, I looked in trac.log and saw no error messages.
The log level is DEBUG.
comment:6 by , 14 years ago
Component: | general → roadmap |
---|---|
Keywords: | needinfo removed |
Have a look at TicketGroupStats in source:tags/trac-0.12.2/trac/ticket/roadmap.py.
You might have a problem with the "overall_completion" setting. The code change between 0.12.1 and 0.12.2 corresponds to: diff:tags/trac-0.12.1/trac/ticket/roadmap.py//tags/trac-0.12.2/trac/ticket/roadmap.py.
comment:8 by , 14 years ago
Here it is:
[milestone-groups] active = * active.css_class = open active.label = Active active.order = 2 closed = closed closed.order = 0 closed.overall_completion = truepercentage testing = testing testing.css_class = new testing.label = Testing testing.order = 1
follow-up: 11 comment:9 by , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:10 by , 14 years ago
Milestone: | 0.12.3 |
---|
comment:11 by , 14 years ago
Replying to cboos:
He he ;-) Nice combination of r10308 and #9711 ;-)
Just change this to a proper boolean value.
Sorry I don't know what you mean … what value should be set to "true"?
If I look at TracIni#milestone-groups-section I don't see such example.
Anything special in your config? Special
[milestone-groups]
perhaps?In general, 0.12.2 works OK for this (see e.g. http://babel.edgewall.org/roadmap which run 0.12.3dev but nevertheless there are no changes in that version concerning the roadmap module since 0.12.2).