Archive for September, 2009|Monthly archive page
New multi Gantt support
Forthcoming Teamwork 4.3 release will support a way of “managing a graphical Gantt-type overview of all projects“, actually, more than this: simply any filter on the project list can be seen in a Gantt-like way, and also printed. The need for this new implementation was suggested on our feedback service and got many votes from our users.
Until now the powerful search filter, which lets you compose complex search criteria, gives as result a simple list of tasks. From 4.3 Teamwork will layout the results also in Gantt graphical style. In the picture below you see an example of it.

Gantt view for Teamwork task's list
In the example above I’ve searched all the active tasks opened after the first of June and with a progress over 50%. Simply picking the “view as Gantt” button I’ve changed the view modality in order to compare the filtered tasks in time.
This cross-project comparison in a unified view is practically impossible (in Microsoft Projects, insert as subprojects etc.) in file-based project management, it is easily accessible in Teamwork instead.
The result of the search will be shown in temporal interval which goes from the minimum start date to the maximum end date, in order to cover all the tasks filtered and to get a global timeline view. Also progress andmilestones are shown. Moreover this page includes the possibility to move in time and to change scale.
![]()
So we keep implementing requests from our feedback service: thanks for the ideas, keep voting there!
More Teamwork – Twitter integrations
Forthcoming Teamwork 4.3 will include among many new features, a richer Twitter integration, extending the existing worklog import/export functionality.
In the picture on the left you see how you can use the tag field to send any issue to Twitter, similarly to delicious. So not only worklog can be sent back and forth between Twitter and Teamwork, but you can send specific issues and worklogs actions to your Twitter account, and also send sticky notes in copy to Twitter, eventually as Twitter answers (“@user”).
In the case of issues, to send the description to Twitter just add “@twitter” in the tags field.
In the issues’ worklog action, put the “@twitter” at the end of the action.
When sending a sticky, you can “CC it to Twitter, as in the picture. Notice that the checkbox “send to Twitter” will appear only if you have enabled Twitter in your user options.
In case you are sending the sticky to a user with Twitter set in options, it will be sent to their attention.
Actually the worklog action trick works anywhere you are writing actions, not only from the issue list, as shown above.
Teamwork webinars
We have just activated the possibility of delivering webinars to customers to remotely supply instruction from our instructors. This is at a fraction of the cost of a bootcamp, and may be all you need. Details can be found here:
Open Lab’s new blog
Open Lab, the software house producing Teamwork, has a new blog here: http://blog.open-lab.com, on the first post we explain the significative positive evolution that we are going through.
Comments (1)





