Xiahung commented on the blog this week that MindManager 9 was adding task durations as "end date-start date" and causing unexpected date-related behavior in his ResultsManager dashboards. I hadn't noticed issues in the pre-release version I'd done some cursory testing on, but Nick Duffill has now determined that changes were made in the final release of v9 to better support use of new Gantt chart capabilities that explain what is going on. Nick has gone to great lengths to characterize the undocumented changes and summarized them in a message in the GTD-MindManager Yahoo group today. I've reproduced his message below for those who are not currently subscribed.
If you are a regular user of ResultsManager, and particularly if you are regular user of MindReader, I would recommend staying with (or moving back to) V8 until this can be addressed by Mindjet or somehow worked around. For example the MindReader "ndd" (no due date) keyword no longer removes due dates. Changing a start or due date with the "m" tage will likely unintentionally shift the other date by a similar amount.
GTD-MindManager post by Nick Duffill:
A brief update for MindManager 7 & 8 users considering moving to MindManager 9,
and for MindManager 9 users who have ResultsManager, or who are using
MindManager for project management.
MindManager 9 has introduced some changes in the way that date information is
handled, which have implications that you should be aware of.
First, it seems that you cannot set a date which is not in the map calendar. So
if the default map calendar only shows Monday to Friday as working days, you
cannot set a date on a topic for a Saturday – it will change to the next working
day by magic. The map calendar must be modified before other days can be used.
"Duration" has changed from being the time that a task will take, to being the
difference in working days between start and end dates. The start date, duration
and due date are now locked to each other. If you change any one, then one of
the others will change to maintain their relationship (subject to the working
calendar rules too). This applies through the software interface as well as
through the user interface, which is proving problematic for ResultsManager use.
The dates that a topic gets might or might not be the ones you entered in the
ResultsManager edit dialogue, for the above reasons. ResultsManager does not
apply the same rules, and at present cannot discover what the rules are through
It is only possible to have topics with only one date on them under specific
conditions now. Generally, if a topic is assigned one date, then MindManager
will ensure that the other one is defined too. We know that a lot of MindManager
users only use the due date.
Lastly, if you change the duration of a task, the due date may get automatically
moved back to suit the duration. If you use due dates to keep track of stuff,
keep an eye on this behaviour. As mentioned, when you edit one of the dates, the
other might move without you noticing.
MindManager 9 has moved from being a fairly flexible system for keeping track of
dated tasks, to something that is more locked down and mainly designed to
support the built-in task management. ResultsManager depended on a flexible
platform, so some users are experiencing problems with the new regime. In
ResultsManager, the start date has always been the first date on which you
wanted to see an action come up in dashboards. This option has effectively gone,
and "start date" now means "the last day that a task can be started, if it is to
be finished on time".
If you have MindManager 8 and are using ResultsManager at present, and rely on
dated tasks in your maps, then it might be worth hanging on for date handling to
be addressed in a MindManager 9 service pack, unless the benefits of MindManager
9 outweigh this.
I'm hoping these issues can be worked through as part of blog series on MindManager Project Management. See MindManager Project Management Part 1 — Project Definition.