Intgreate Features Server with Atrium,Case Tracker

I was playing around with integrating Atrium and the Features Server feature and thought I would share my basic process. This is in no way perfect but it's a start. Please add on other useful pieces of information.

1. Install Atrium.
2. Download the Features Server feature. DO NOT INSTALL YET!
3. Add the following line to fserver.info: spaces[types][] = "og"

This allows the feature to be integrated with Organic Groups with any other configures or coding. (Ref: http://openatrium.com/build_a_feature #4)

4. Install the feature and Clear the cache.

5. This features adds several items but we are going to focus on the 2 new content types (fserver_project, fserver_release) and the context (fserver-section-project).

6. Change the Display name of the fserver_project from "Project" to "Feature"

We want to leverage the project in case tracker. This will help make the interface cleaner.

7. Change the title of the fserver_release CCK field field_fserver_project to "Feature" to match the content type change.
8. Add a CCK field to casetracker_basic_case.
   • Title: Feature/Feature Release
   • Node Reference
   • Autocomplete Widgit
   • Add a reference to Feature and Feature Release content types. This will allow you to attach a case to the feature or the release.
9. Edit the fserver_projects view

• Change the Empty text to "There are currently no features available."
• Change the title to "Features"

TO DO

• Add a 40x40 logo following #9 on this page: http://openatrium.com/build_a_feature
• Add more content (views/blocks) to fserver context

Like I stated at the beginning. This is not the only way to integrate and it's not complete either. I'm still doing workflow testing.

This is in by no way the only way to do it. I've attached some screenshots. One very cool unintended feature is that the released cases are shown on the feature page.

Many thanks to Development Seed for producing a few great products.

Cheers