Redmine

Gustav Vella wrote:

By default issues/tasks assigned to a milestone are not grouped by milestone but displayed ungrouped above the list of all the milestones (cf. attached png).
Is this a redmine flavor of Gantt or a bug?

Actually, it is currently implemented in a slightly different way. The issues on the Gantt-chart are "sorted" by the start-dates of the individual issues (Redmine currently assumes that each issue has a start-date (see issue #3011)). The versions are "sorted" by their due-dates.

• Usecase 1: Let's say you have four versions (all having a due-date in june 2009 (see issue #184)) and four issues of which each is assigned to one of the four versions. These four issues are all having a start-date of 19-05-2009. In this case the issues aren't "sorted by the listed versions". Instead they are displayed as shown in your screenshot indeed.
  
• Usecase 2: Let's say you have four versions (all having a due-date in june 2009 (see issue #184)) and four issues of which each is assigned to one of the four versions. These four issues are all having a start-date of 1 day before the due-date of the assigned version. In this case the issues are "sorted by the listed versions" due to the fact that the issues have a start-date which lies before the assigned versions due-date.
  
• Usecase 3: Let's say you have four versions (all having a due-date in june 2009 (see issue #184)) and four issues of which each is assigned to one of the four versions. The latest two of the four are having a start-date of 19-05-2009. The first two have a start-date of 1 day before the due-date of the assigned version. In this case the first two issues are "sorted by the listed versions" due to the fact that the issues have a start-date which lies before the assigned versions due-date. The last two issues aren't "sorted by the listed versions" since their start-dates lies before all other Gantt-parts (issues and versions).
  

See also issue #347 for a feature request regarding the described behaviour.

I agree this should be documented. I'll add it to the wiki extensively soon... :)

Kind regards,

Mischa.

I personally would like the tasks to be grouped by roadmap -- irrespective of the start date (even display a task with a blank start date - I would like the start-date to mean the date we start working on something). Would it be acceptable to allow (even it if not the default but a checkbox option on the side bar)?

1) Gantt grouping by Roadmap

2) Display all tasks in a Roadmap -- even if no start date (it would not need a progress bar since no progress has started -- just to be listed so we can see that we have a problem with the timeline and what is underway). I am hoping that I can eventually use the start date to indicate when a task is started -- and not have to have start tasks in order to control the display.

3) Allow tasks to see/be attached with "Parent Roadmap/Versions" and to have tasks in Sub-projects be displayed and grouped by the Parent Roadmap items.

Hopefully, these make sense and would be acceptable. In the meantime. I will change the start dates so tasks are displayed/grouped appropriately. I look forward to understanding if these are interesting ideas.

Thanks,

Bill

I agree with 1) and 2). They are valid for some settings and work approaches. They would apply for ours. I can't really understand 3).

Regarding blank start date: Is there any way of switching the default start date = date issue is opened to just blank?

Kind regards
Gustav

Sorry that Item 3 was not clear -- I will try again:

Parent Project -- Core network Upgrades 
     A project the managers use to track the entire project and associated documentation, 
     with the following versions:
     VERSIONS
     * Phase 1 - (fix primary risks)
     * Phase 2 - (fix secondary risks)
     * Phase 3 - (fix performance issues)

  Sub-Projects
     Projects the techs use to manage the actual technical work between various people and technologies 
     (each of these projects and the associated tasks is aware of the "Parent Project" versions and will 
     displayed in the appropriate version grouping in the Gantt chart.
     * Firewall upgrade
     * Core switching upgrade
     * Authentication integration

Hopefully this makes more sense now. I cannot otherwise see how to use Redmine to manage a large complex project with many sub-projects -- which is a task we are currently facing. (Other ideas would be appreciated if this change/improvement would be unwise).

Thanks,

Bill