Open Atrium

I'm a big fan of Panopoly and, in the past, I've been a big fan, user and builder with OA1. Just watched this lovely developer demo video here on OA2: https://vimeo.com/64411430 and installed alpha2 version. Really love it and so excited to be working on OpenAtrium again in Drupal 7.

Hello Everyone!

The Bucket Brigade is sponsoring me to build a Work tracker for Open Atrium 2.0 (similar to the Case Tracker in Open Atrium 1.0).

I've only just started development yesterday, so it's still super early. However, I wanted to show you what I've got, tell you about our plans and invite you to contribute your ideas, bug reports and patches!

Here is the project page:

http://drupal.org/project/oa_worktracker

(NOTE: A development release should appear in a few hours!)

Architecture

We are looking at installing and using Open Atrium as an extranet in my organization. Organizationally we always like to have a support agreement with a third party for assistance and advice as needed. Has anyone had any experience with support for Open Atrium from companies like Acquia, Phase2, etc?

Thanks!

Hi everyone, I have many users in my db, and i don't want all users subscript to the group. Just if i have group so users can post the case the the group. does anyone know about this?

Hello folks, I've been trying to get a handle on my perspective as the latest maintainer of OG's 6.x branch. There is an entire, gigantic issue queue with ideas of what's wrong and where folks would like it to go. As I've tried to curate the queue, I've come to realize there should probably be some kind of discussion.

OG6's sun has already started to set, but it remains in use on thousands of websites. It's biggest challenges are not in exploring new features, but in supporting existing websites and new, stability-critical D6 websites by cleaning up the many warts: unexpected or incomplete behaviors, usability-challenged workflows, performance improvements, low-impact integrations with common modules (Features, etc), and if possible more thorough coverage by automated tests.

As mentioned in the Issue Queue, 6.x-2.2, with a slow year of enhancements and bugfixes, is almost ready. All that waits is fixing the broken tests and reverting Notifications 4.x support back to the more stable, known Notifications 2.x line.

What should be done after that?

I began the install and got though the following steps:
*Choose profile
*Choose language
*Verify requirements
*Set up database

Following the database install, preparing for profile install I get the error:

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM atrium_menu_router WHERE path IN () ORDER BY fit DESC LIMIT 0, 1 in /var/www/atriumcore_new/includes/menu.inc on line 315 (see below).

We needed to be able to group Tickets within Open Atrium as backlog items to be organized into Iterations. After considering ways to emulate that with the stock Open Atrium architecture, I decided to just create the functionality and encode it as a Feature. The result is Open Atrium Iterations.