export to MS project after pushing tasks to Mindjet

  • 1
  • Problem
  • Updated 5 years ago
Windows 8 / MS Proj 2003.
1. Set up a MM map & task with start & end date, resource allocation and resource loading.  Exports all info to MS Project fine.

2. BUT, if you push task to Mindjet, you lose the resource loading, affecting MM Gantt chart & utilisation calculations. Fixing every task resource allocation after export to Mindjet would be tedious to say the least.

3. Exporting any map that has tasks exported to Mindjet.  When you export map to MS Proj, the tasks that have been exported to Mindjet lose their duration, appearing in MS Proj as a zero day milestone.  Fixing every task in MS P would be tedious, especially if you update the map and re-export to MS P.  This is compounded by the loss of resource loading mentioned in (2) above. 

Are either of these issues known problems or can they be dealt with by set up choices in MM?
Photo of Jamie Foale

Jamie Foale

  • 2 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 1
Photo of Jamie Foale

Jamie Foale

  • 2 Posts
  • 0 Reply Likes
On further digging on point 3.
Help shows that MM Project export does not use end date, rather uses start date and specified duration.  Duration is automatically generated by MM when start/end date specified.  The issue is that when task is pushed to Mindjet, the duration field disappears (despite start and end dates surviving).  Once pushed to Mindjet, duration field is greyed out and cannot be edited.  Therefore task appears in MS Proj as start date only.

Why cant the export to Proj function utilise the end date? Or why cant the duration field survive export to Mindjet?