Opened 17 years ago
Last modified 17 years ago
#1731 new enhancement
Biling and other reports do not reflect a retargeted ticket
Reported by: | Owned by: | Russ Tyndall | |
---|---|---|---|
Priority: | low | Component: | TimingAndEstimationPlugin |
Severity: | normal | Keywords: | |
Cc: | mlists@…, th07@… | Trac Release: | 0.10 |
Description
Not sure if this is possible but, currently when a ticket is retargeted to another milestone the plugin reports on the total hours associated with the ticket. It would be nice if you could view hours for a given milestone if a ticket spans multiple milestones.
I have logged a related bug against trac which deals with the fact that re targeting does not get reflected in a tickets change history: http://trac.edgewall.org/ticket/5658#preview
Attachments (0)
Change History (4)
comment:1 follow-up: 3 Changed 17 years ago by
Priority: | normal → low |
---|
comment:2 Changed 17 years ago by
Cc: | mlists@… added; anonymous removed |
---|
Thanks. I am looking at supporting Agile Development teams using milestones as sprints. My guess is that you would not see the a ticket moved more than twice.
Mike.
comment:3 Changed 17 years ago by
Cc: | th07@… added |
---|
Replying to bobbysmith007:
I will think about it and leave the ticket open though. There might be a way, but if it changed numerous times, it might be difficult to get cross platform sql that will handle that.
Have u found any solution to this issue? I've developed TimeVisualizerPlugin. Retargeting tickets or renaming milestone is major problem for my burn down too. If there is any feasible workarounds available, please let me know. I'm cross referencing to this ticket from my issue #1977.
comment:4 Changed 17 years ago by
Sorry, as best I can see, in the current version of trac, there is not a way to do this that doesn't involve a tremendous amount of work.
If you come up with something, let me know and I am happy to attempt an implementation or apply a patch.
Russ
hmmm... Sorry I missed this, but I don't think there is anything I can do about this without making the reports massively more complex. I will think about it and leave the ticket open though. There might be a way, but if it changed numerous times, it might be difficult to get cross platform sql that will handle that.
Russ