Modify

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#9704 closed defect (fixed)

Milestones without dates are not properly scheduled in ASAP mode

Reported by: ChrisNelson Owned by: ChrisNelson
Priority: normal Component: TracJsGanttPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11

Description

As discovered in the course of #9566, in ASAP mode, a milestone without an explicit due date shows up today, aligned with other leading tickets, not after the tickets it depends on.

Attachments (0)

Change History (8)

comment:1 Changed 3 years ago by ChrisNelson

  • Status changed from new to assigned

comment:2 Changed 3 years ago by ChrisNelson

(In [11160]) Use ints, not strings, when setting dependencies on milestones. Refs #9704.

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

Hey, I've noticed with r11160, it's shows up properly! The milestone with date is at its right position inbetween the tickets and the one without date shows up after all tickets at the bottom of the chart on the most right-hand side. Thanks. Either [11159] or [11160] did the magic.

comment:4 in reply to: ↑ 3 ; follow-up: Changed 3 years ago by anonymous

  • Resolution set to fixed
  • Status changed from assigned to closed

Replying to falkb:

Hey, I've noticed with r11160, it's shows up properly! The milestone with date is at its right position inbetween the tickets and the one without date shows up after all tickets at the bottom of the chart on the most right-hand side. Thanks. Either [11159] or [11160] did the magic.

Glad it worked for you. I've been knocking off a lot of little issues lately. It helps to have someone outside my organization giving me prompt feedback. Thanks.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 3 years ago by falkb

Replying to anonymous:

Glad it worked for you. I've been knocking off a lot of little issues lately. It helps to have someone outside my organization giving me prompt feedback. Thanks.

I like the idea of having something in the end that is usable, and having something that maybe can replace those MSProject plans (at least for the programmers) since tickets are already used to setup work packages and split them into sub tasks by child tickets. If even data export/import was possible, it could avoid doubled work... still a long way to go... maybe not possible at all. I also see difficulties mainly in separating task data into plan and reality (see #8786). But I believe in the power of this TracJsGanttPlugin project; you've got an awesome boost of functionality improvement, this project is very alive.

comment:6 in reply to: ↑ 5 ; follow-up: Changed 3 years ago by anonymous

Replying to falkb:

Replying to anonymous:

Glad it worked for you. I've been knocking off a lot of little issues lately. It helps to have someone outside my organization giving me prompt feedback. Thanks.

I like the idea of having something in the end that is usable, and having something that maybe can replace those MSProject plans (at least for the programmers) since tickets are already used to setup work packages and split them into sub tasks by child tickets. If even data export/import was possible, it could avoid doubled work...

I really hate duplicated work and that is driving me to make this better.

You can create a project plan in Microsoft Project, export it to CSV, and use Ticket Import plugin (with a patch I posted) to import the dependencies into Trac. I don't know of any way to go back, though.

still a long way to go... maybe not possible at all. I also see difficulties mainly in separating task data into plan and reality (see #8786).

It's a ways off but I see that as quite practical. You can query the Trac db for ticket data as of a certain date so your "baseline" just becomes a point in time and TracPM can query then and now and show you the difference. I'm not saying it's not a lot of work but the data is all there already and I see value in that.

But I believe in the power of this TracJsGanttPlugin project; you've got an awesome boost of functionality improvement, this project is very alive.

comment:7 in reply to: ↑ 6 ; follow-up: Changed 3 years ago by falkb

Replying to anonymous:

You can create a project plan in Microsoft Project, export it to CSV, and use Ticket Import plugin (with a patch I posted) to import the dependencies into Trac.

Thanks, it's a good hint, I didn't know that.

I don't know of any way to go back, though.

I see that MS Project can load from CSV file. Maybe it's a good idea to export from the gantt chart to CSV, isn't it?

comment:8 in reply to: ↑ 7 Changed 3 years ago by ChrisNelson

Replying to falkb:

... I see that MS Project can load from CSV file. Maybe it's a good idea to export from the gantt chart to CSV, isn't it?

One of my long-term TracPM objectives is a WBS editor like Project's WBS/Gantt view. It'd be a wrapper around jsGantt which would add checkboxes on the left to select tasks and some buttons above or below to link, unlink, etc. I imagine something like /wbs?<selectioncriteria (e.g., /wbs/root=1234) would display such a page. An <<Export>> button there would be nice.

Add Comment

Modify Ticket

Action
as closed The owner will remain ChrisNelson.
The resolution will be deleted. Next status will be 'reopened'.
Author


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

 
Note: See TracTickets for help on using tickets.