Opened 19 years ago
Closed 19 years ago
#2941 closed defect (fixed)
Clicking on milestones progress bar should not use hardcoded list of ticket status
Reported by: | Owned by: | Alec Thomas | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11 |
Component: | roadmap | Version: | devel |
Severity: | normal | Keywords: | workflow |
Cc: | guillaume.tardif@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
In the new workflow implementation (WorkFlow), it is possible to customize the list of available status for tickets.
If we add the correct list of possible ticket status in the trac DB, then the custom query page displays them correctly when using "status" as a query criteria. (see #2898)
However, when using the milestone view and clicking on a ticket progress bar, trac redirects to the custom query page with search criteria on the "status" field that use a hardcoded list of status.
When clicking on the "closed" (white) part of a progress bar, we get all closed tickets, but when clicking on the "not closed" (green) part, we get all ticket in status "open", "assigned" and "reopened".
This is hardcoded in trac/ticket/roadmap.py, lines 54 and 61. I think it here should get all status values from the DB except "closed" (unfortunately I'm not a python developer myself, someone else will probably be much quicker than I to correct this)
Attachments (0)
Change History (4)
comment:1 by , 19 years ago
Description: | modified (diff) |
---|
comment:2 by , 19 years ago
Status: | new → assigned |
---|
I'll fix this up after the latest API changes are merged (should be in the next couple of days).
comment:3 by , 19 years ago
Keywords: | workflow added; Workflow removed |
---|---|
Milestone: | 0.10 → 0.11 |
comment:4 by , 19 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
It is no longer necessary to add states to the database, so you will probably have to remove those you added manually. See #2898 for more details.
I've also fixed the roadmap, in r3065, so it effectively builds the query using status!=closed
. Let me know if this doesn't fix your problem.
(Note that there are currently some minor issues with creating new tickets. These issues will be fixed shortly)
Please don't use
[[BR]]
for paragraph breaks. Put a blank line between your paragraphs for proper formatting.