#1913 closed defect (fixed)
0.11 workflow compatibility
| Reported by: | bewst | Owned by: | Russ Tyndall |
|---|---|---|---|
| Priority: | high | Component: | TimingAndEstimationPlugin |
| Severity: | critical | Keywords: | |
| Cc: | aqualx@… | Trac Release: | 0.11 |
Description
In the reports I see conditions like
t.status IN ($NEW, $ASSIGNED, $REOPENED, $CLOSED)
but for 0.11 all reports with
status IN ('new', 'assigned', 'reopened', 'closed )
got upgraded to
status <> 'closed'
If you don't make a corresponding change, tickets disappear from reports when their status becomes 'accepted', and presumably the new workflow means tickets can go through any number of other states. I think this fact leads naturally to reconsidering the appropriateness of the status checkboxes in the query UI.
Attachments (0)
Change History (9)
comment:1 Changed 17 years ago by
comment:2 Changed 17 years ago by
| Cc: | aqualx@… added; anonymous removed |
|---|
comment:4 follow-up: 5 Changed 17 years ago by
type /query after your main url , or click the "Custom Query" button on the "View Tickets" screen.
hth, Russ
comment:5 Changed 17 years ago by
Replying to bobbysmith007:
type /query after your main url , or click the "Custom Query" button on the "View Tickets" screen.
You can't use the query interface to get almost any of the useful reports. For one thing it queries by ticket, not by ticket change. For another thing there's no way to get e.g., the total hours worked by an individual. For another, there's no filtering by billing period.
But that should be obvious to the person who created the TimingAndEstimationPlugin (you had to build some pretty complex SQL queries), so I'm wondering if somehow I'm missing something.
comment:6 Changed 17 years ago by
Yeah, It certainly doesnt fix everything (or even much of anything), but its is the best I can do until I can figure out someway to make this work. Last I worked on it, I could not come up with an elegant solution to this. Still thinking about it, but with no answer.
Sorry I cant be of more use, Russ
comment:7 Changed 17 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
After much waiting and thinking, I came to the conclusion that the best way to handle the dynamic statuses was to rebuild the reports each time they change. To that end I have added code to check to see if the statuses have changed and then update the reports with the new statuses every time they change (requiring a trac-admin upgrade). Rendering out the statuses and the linkifying javascript were changed to be compatible with this.
Yeah. I will look at making this database driven in the future so that it will work. Might be tough, but I will see what I can do.
In the mean time, check out the /query interface, to see if you can accomplish what you need.
Russ