This project is not covered by Drupal’s security advisory policy.
This module is currently in alpha. Use at your own risk.
Original feature request issue: http://drupal.org/node/826490
The original use case for this module required the ability to set up groups in Open Atrium with a choice of project "templates" with pre-populated cases. The projects and cases required a number of additional fields and so View Datasourse and Feeds XPath Parser allow for this in a very flexible fashion, via XML. This could, eventually, allow for importing from alien project management tools, such as Redmine.
Default views and feed importers are provided, so this module is fairly straight-forward to setup. Documentation is currently lacking, due in part to a lack of time on my part, but also to my lack of perspective. That is, it all looks pretty obvious to me, but then I know where everything is. Please file issues to help me fix it.
For easiest setup, CT_Feeds needs to be installed on both the source and destination sites. Case Tracker needs to be set up in the usual way (that is create content-types for projects and cases, and assign them at
/admin/settings/casetracker/settings). Create some sample projects and cases on the source site.
The project feed importer (
<destination_url>/admin/build/feeds/edit/projects_feed) will have to be attached to the content-type you just created for projects. You can then import projects via the 'Projects Feed'(
<destination_url>/import/projects_feed), and point to the URL exposed via Views on your source site (
<source_url>/feed/projects). This will create projects that are themselves the feeds for their associated cases. You can then trigger the import of those cases when viewing the actual projects (triggering this will eventually be automated). Case states that don't exist on the destination will automatically be created.
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Import/Export, Project management, Syndication
- Downloads: 988
- Last modified: November 28, 2014
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.