Modify

Opened 3 years ago

Last modified 21 months ago

#9279 new defect

start date in chart different to set start date in ticket

Reported by: falkb Owned by: ChrisNelson
Priority: normal Component: TracJsGanttPlugin
Severity: normal Keywords:
Cc: rjollos Trac Release: 0.12

Description

I have a ticket which is parent of other tickets and it has set fields.start and fields.finish. I understand both fields as they are for setting the planned range of time.

But the chart don't display the given start date in column "Start Date" correctly, but it seems to compute a new start date from "End Date" minus worked hours. That confuses us when reading the chart as plan.

BTW: on several places it's not clear in the chart what is just data of plan/schedule and what is data of the past reality. This should be clearly distinguished by the chart, maybe by colors. This is somehow related to #8786.

Attachments (0)

Change History (5)

comment:1 Changed 3 years ago by rjollos

  • Cc rjollos added

comment:2 follow-up: Changed 3 years ago by falkb

This patch fixes the chart to used the given planned start date for displaying the ticket bar, instead of any calculated start date by "finish date minus duration":

  • C:/tracjsganttplugin/0.11/tracjsgantt/tracjsgantt.py

     
    641641 
    642642                # Set the fields 
    643643                t['calc_finish'] = finish 
    644                 t['calc_start'] = start 
     644                if (t[self.fields['start']]): 
     645                    t['calc_start'] = datetime(*time.strptime(t[self.fields['start']], self.dbDateFormat)[0:7]) 
     646                else: 
     647                    t['calc_start'] = start 
    645648 
    646649            return t['calc_start'] 
    647650 
     
    723726 
    724727                # Set the fields 
    725728                t['calc_finish'] = finish 
    726                 t['calc_start'] = start 
     729                if (t[self.fields['start']]): 
     730                    t['calc_start'] = datetime(*time.strptime(t[self.fields['start']], self.dbDateFormat)[0:7]) 
     731                else: 
     732                    t['calc_start'] = start 
    727733 
    728734            return t['calc_finish'] 

Anyway it's a hack, but I expect to see the ticket plan in the chart. In the end the chart sources must be reviewed to clearly distinguish between displaying the datetimes and time ranges of plan and reality.

comment:3 in reply to: ↑ 2 Changed 3 years ago by anonymous

Replying to falkb:

This patch fixes the chart to used the given planned start date for displaying the ticket bar, instead of any calculated start date by "finish date minus duration":

Well now after my update to [10928] this patch doesn't work anymore either. Now I see the plugin behaviour that start time of a ticket is always the calculated. That overrules all given start dates I have set in the 'start' field of the ticket, and this overruling is a bug.

comment:4 in reply to: ↑ description Changed 3 years ago by falkb

Replying to falkb:

I have a ticket which is parent of other tickets and it has set fields.start and fields.finish. I understand both fields as they are for setting the planned range of time.

But the chart don't display the given start date in column "Start Date" correctly, but it seems to compute a new start date from "End Date" minus worked hours. That confuses us when reading the chart as plan.

Checked it again with today's version (see #9653). That wrong behaviour still happens.

comment:5 Changed 21 months ago by ChrisNelson

The problem here appears to be that rather than honoring user-supplied start and finish for groups, I bubble-up the earliest child start and latest child finish. I'll come back to this, but I don't know how soon.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.