Teamwork currently (3.2.8) supports a built-in, we’ll call it “standard”, authentication (notice that Teamwork works fine also under https) , which is the usual login, and authentication provided by the container, we’ll call it “http authentication”. This allows both single-sign-on support and also LDAP authentication through say the Tomcat container, as detailed in the forum.

We are empowering authentication with a third modality, by having Teamwork contact directly the LDAP server, and also importing and updating users from LDAP via a scheduled job if needed. All this includes Active Directory; in this way, your LDAP will be the source of users and authentication. This third modality we’ll call it “LDAP”. It will make integration very easy, feasible completely just through the web interface. :-)

If users will require it, it will be quite easy to integrate also OpenId authentication.

UPDATE: Teamwork 3.2.9 includes direct LDAP import and authentication: see

Labels: authentication, ldap, TeamworkTalk

Today we completed integration between Teamwork agenda and Google calendar.
In the original project we just dispatched events created in Teamwork to Google calendar, but now we let users export a complete Teamwork agenda in Ical format in order to see all appointments on another calendar server (just like Google calendar but also in another Teamwork!).

Another added feature lets you import one or more external calendars in Ical format and see the events contained in it inside Teamwork’s agenda.

While building the integration, I’ve had all sorts of troubles with date format and time zone settings. In fact we couldn’t assume that calendars working together have the same time settings, so it was necessary to convert dates in the correct time zone every time we tried to do an export or an import.

Now everything works fine and it’s great! You can send every new event created in Teamwork to your Google calendar, you can see all your Google calendar events simply copying the given calendar’s address in Teamwork, and you can also do the opposite!

Labels: TeamworkTalk

Among the rich set of integrations possible with Teamwork, one which we are considering is integrating Alfresco document management with Teamwork's. We were discussing this at a customer (a bank), when they showed us that Alfresco provides file system network access to its document engine, so you can access the document tree throuh the network just by tipying a network address of the form \\alfrescoServer\... . Well then we immediately created a file storage pointing to the root of the alfresco server, so that the area manager can set on tasks roots the document root corresponding to it, and operate! So the inner flexibility of Teamwork gave us immediately a first, rough "integration" with Alfresco, which the customer loved, and makes them immediately operative.

Labels: Alfresco integration, TeamworkTalk

Yesterday we tested Teamwork’s automatic Ical calendar export, by having a user with a Gmail e-mail, so that instead of downloading the Teamwork generated Ical message, it was Gmail getting it: it works perfectly. So this kind of synchronization of Teamwork and Google calendars works right now, with the current release (3.2.8), and without any effort from the user: she just writes her Gmail e-mail on her Teamwork user, creates appointments in Teamwork, and gets them almost immediately in her Google calendar.

Labels: TeamworkTalk

In the path of becoming the most open, integrated and widely compatible project management application there is, we are integrating Google calendar with Teamwork's shared agenda, adding this to ICal/Outlook integration. Our Silvia is following this; see her on Twitter. Stay tuned for this and other additional integrations!

Labels: TeamworkTalk

We are currently working on expanding and improving Teamwork’s capacities in “listening” to other applications, and “talking” to them. The improvements will be progressively released. In particular:

Project clients
MPX support has been improved, so that imports and exports can be done from and to localized versions of MPX’s. This is compatible with GanttProject (http://ganttproject.biz) and Microsoft Project formats and behavior (this improvement is included in release 3.2.7).

Data export
You already have the export to PDF functionality; we’ll add that all your filter/lists will be exportable in CSV format.

Listening to work logging
We are developing a functionality to import work log from different sources: one is Twitter (http://twitter.com), another one is Subversion commits (http://subversion.tigris.org), a third one is CVS commits (http://www.nongnu.org/cvs). The Twitter module will also let export Teamwork work logs to Twitter. The Subversion and CVS modules will also integrate in the file storage, allowing web access to repositories.

Synch of agendas
Ical (and hence Outlook) synchronization has been a will be further improved. We are also working on synchs with Google’s calendar.

A bit of mystery
There are other directions in which we are working, but are still in early alpha stage: let’s just say that we intend to facilitate migration from “data hostage” environments to our open structure.

Above image link.

Labels: TeamworkTalk, Worklog and data exchange

Project management and e-mail communication have a love-hate relationship; on the one side, e-mail is a bad idea for handling projects: A 10-to-1 rule of email based project management, and on the other side, it is the most comfortable mean of remote communication and information transmittal, sometimes even better then the browser, as it given less remote access problems.

Labels: Java Outlook ICalendar Agenda TeamworkTalk, Project management by e-mail, Teamwork by e-mail, TeamworkTalk