Opened 12 years ago
Last modified 12 years ago
#10697 new enhancement
datetime of closed should set implicit enddate of ticket (if not explicitely given)
Reported by: | falkb | Owned by: | Chris Nelson |
---|---|---|---|
Priority: | normal | Component: | TracJsGanttPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: |
Description
Most closed tickets here have no explicitely given enddate or startdate. They just align to its parent or to its milestone.
I wish in such case the timestamp of reaching the 'closed' state can implicitely set an enddate.
Don't know if it fits to the current approach of the system; if not valid, you can simply close this one with 'wontfix'.
Attachments (0)
Change History (2)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
On the other hand, the system must consider the ticket dependencies for aligning. No real idea how to solve this problem. After all it's just a feeling of having more comfortability with that desired enhancement.
You can see it in /attachment/ticket/10686/TH10686-with-hours.png if you expand ticket 299. 299 is just a container of lots of tickets, and its tickets would better align if the 'closed' datetime is more considered, you know.
I have a local patch which shows "actual" dates (first transition out of "new" as start and last transition into "closed" as finish). It's rather experimental and a bit large. I need to at least make it optional (something like
showactual=1
) before pushing it to TH.