![ganttproject date problem ganttproject date problem](https://blog.bqe.com/hs-fs/hubfs/Imported_Blog_Media/gantt-chart-1.jpg)
Environment: latest redmine0.9stable, sqlite3, webrick, virtual pc with 1.5GB. I'll try and fit in testing the plugin on the same MS Project XML file todayĪlternatively I'll try it straight away, and ignore Java for a while. But import/update is the top priority now, I'll think about exporting when I get there :) What about export? It could be really useful if I can plan my project on MS Project, let my users interact with RedMine and periodically download an export for MS Project for review. So updating should work, I still hope there won't be too many problems in case the original project file gets re-arranged too much, as I don't know a thing about how GanttProject (or MS Project for that matter) internally manages the task ids.Īlso, I'm still thinking about what options for updating/synchronization are required, like if the importer should preserve (or maybe explicitly delete) the comment history on issues and whatever things one might want. Last evening was mostly spent on looking into and extending the built-in issue model of Redmine, where I added a field to each issue to identify the original task id it was imported from.
GANTTPROJECT DATE PROBLEM UPDATE
Is your plugin able to update tasks or does it perform the initial import only? Generally speaking, the XML generated by the GanttProject exporter isn't that different from the GanttProject files, so it wouldn't probably be that hard to simply write another import method after the whole infrastructure is working. For any more functionality, I'd have to rely on any sample files you or someone else could provide. I don't want to promise MS Project support yet, as I could only use exported GanttProject files to test it. I can provide italian translation if it works with MS Project files too.
GANTTPROJECT DATE PROBLEM CODE
This code updates our start dates adding a day to theirs start date. This is where we have the trouble.įor example: at the beginning of a project we have some tasks having a duration less than a day so they have the same start date. We have seen this methods make that TYPE_PRECEDES relations can’t start the same day. (issue_from.due_date || issue_from.start_date) + 1 + delay Return nil unless (TYPE_PRECEDES = self.relation_type) & (issue_from.start_date || issue_from.due_date) Issue_to.start_date, issue_to.due_date = successor_soonest_start, successor_soonest_start + issue_to.duration If soonest_start & (!issue_to.start_date || issue_to.start_date < soonest_start) Soonest_start = self.successor_soonest_start We are having some problems with task relations due to validation on model (\app\models\issue_relation.rb): def before_save We are developing the Microsoft Project file import/export utility as a plug-in for Redmine.