The Project page mentions: "Date and end date fields in tasks and project can't be empty"
This is a problem for either ongoing projects without an end date, and for categories like "general' which don't have start and end fields.

CommentFileSizeAuthor
#1 ongoing_project_fix-2291985-1.patch14.02 KBdobe

Comments

dobe’s picture

StatusFileSize
new14.02 KB

Hello Yuri,

The request you bring up have two separate issues around them. The first being how Views Gantt deals with a task with no Start or end date value. We had a similar request from one of our clients. The request was that the client did not want to necessarily set an end date. Which would be viewed as an ongoing project/task. Which is a valid and logical real world issue.

The current version of Views Gantt does not like dealing with tasks that don't have a start date or end date value. It currently flags the task row with something similar to "*START/END DATE MISSING*".

The patch attach solves this problem by allowing you to set a date range for the view. Which in our case seemed to be the best (may not be) way of dealing with this issue. Which we then say if the start or end date has a NULL value then set fake date(s) past the date ranges.

The second issue that your addressing, Being able to set a "project" to an entity that does not even have start or end date fields. This idea would be a fundamental issue, as a gantt chart is used to deal with the display of time. But hey we are dealing with drupal here so let's address that issue without having to modify the Views Gantt.

If your wanting to display a gantt chart on a taxonomy term or a entity that does not contain start or end date fields all together. What you can do is build a views gantt chart based on the context of that entity. Instead of trying to use that entity as the "project" for the gantt. As it sits project is not required. SO you could pass in a contextual filter (say for the taxonomy term id) and grab all your tasks that are referencing that term and build your gantt view from that data instead. This will completely bypass this issue all together.

Enjoy,
-Jesse