Teamwork release 4.3 available for download

Teamwork 4.3 multi-Gantt view.
Teamwork 4.3 multi-Gantt view.

A free upgrade release for all users of version 4.0-4.2, this release includes some major extensions of functionality; while there is no “revolution”, this kind of release makes your “Teamwork life” more comfortable. Several features requests from the feedback service have been fulfilled. Also the user guide has been updated.

Download this release here.

Multi-Gantt support

This was motivated by this request: “Manage graphical Gantt-type overview of all projects”. We then realized that all it needed was the filtering power of projects search together with a Gantt style visualization. So this is what we’ve done: we added an additioanl visualization of the search results. So for example you can see all your root open project closing in 2 weeks in a Gantt style view.

Also all the Gantt scales have been extended to 5 years.

Import from CSV – Bugzilla

Import of issues and resources from CSV files: issues get imported from the Bugzilla CSV export format, but of course in this way you can import from anything.

Collapsible project trees

Projects trees can be collapsed and there are options to keep them open by default etc. . This was this request; thanks to Halil for the first implementation.

More Twitter integrations

Twitter integration with any action and there is a new portlet for filtering tweets on any topic: see the user guide, section 8.3.3.

Little improvements

– All notifications have in the subject the task they refer to, if it exists (this request).
– Display log on descendants (this request).
– Balloons have no more the confusing Roman number.
– UseĀ  darker gray on Gantt duration background – better prints.
– Search analysis worklog: make the field “action” larger.
– In resource list there is no more the bothering default filter by company.
– Snapshot of a task can be edited.
– Search analysis worklog: make the column “action” larger.
– Issue multi editor: if there is a task on the issue and you have an assignment on it, let the watch icon appear even if the issue is not assigned to you.
– Experimental: supporting SSL over LDAP (LDAPS)

Bug fixes

– Issues didn’t get indexed any more for full text search.
– Order in company news doesn’t work.
– Portlet news doesn’t show news ordered by order factor.
– Resource hourly cost sometimes gets set to zero.
– Meeting: drag&drop multi editor doesn’t work for the just inserted.
– The link to resource drawn by the smart combo if the resource is from another area on which you have no right you see the link but you get an error.
– Search of a string containing ” in issues looped the application.
– Sometimes the rollover menu opened in the wrong direction.
– If you change the allowed file storage roots, disable links to old locations.

Technical notes for upgrade

This release build is 11250; it contains no database schema changes for all users of 4.2.10080 and following. As it contains an issue full-text indexing fix, you should reindex your data: see 17.4 of the user guide.

try darker gray on gantt duration background

What you get with Teamwork and what you don’t

featuresSome project management applications provide minimal functionality: just a Gantt drawer. Some, more groupware oriented, provide a vast spectrum, including e-mail and chatting. While developing Teamwork, we made several choices about what to include and what not. The choice for Teamwork has been guided by this simple princliple: include only what will not sharply conflict with acquired user habits, and will have a rich integration with the rest of the system.

Examples of what we did include:

– “boards”
– sticky notes
– to-dos
– a calendar

All these have a natural integration with project management, bringing together personal and team management. So we put them together in a unique, integrated solution; you don’t have to get three separated products from us to get this functionality.

Examples of what we didn’t include:

– e-mail client
– chat services
– file management

The three integrations above are probably used by most in standard ways, and happily too: you are not going to change those user habits with the new project management software; so the work we have and are doing is to integrate with the existing applications, as smoothly as possible.

Notice also that probably most users already have a calendar application, and others that may overlap with what we provided built-in, and for that we are working so hard in extending seamless integrability (most previous posts talk about this in fact).

Current and future developments

Wikipedia logo
Wikipedia logo

This is for the actual situation; but usage of the web is evolving all the time, and more integrations are now needed: in Teamwork we always assumed that the contents and documents related to projects and work which would not be articulated in tasks, issues and to-dos would be handled by other document management software, and then somehow connected to projects (say for example with file storages). But with wiki and blogs, content is more and more inserted directly online, and we should support this also inside Teamwork. One can currently do this by simply creating custom portlets connected to a Wiki service. But as with most of our solutions, we would like something organically integrated with the rest of Teamwork functionality; for example, content editing would naturally blend with exposure of Teamwork objects to REST and similar services, and in-place customizations of pages. So this is one of the (non trivial) directions we are now exploring.

If there is an organic integration that we are missing, just post it on our feedback service!

The quoted products, services and images may be registered
trademarks of their producers.
Images that require attribution are linked to their source.