Doing better than the usual project management software?
How can we improve Teamwork, and more in general, how can we help people and teams manage their work better and better?
Teamwork today is a stable, well known and widely used application – its sales getting better every month. We are always improving it and searching for new ways to make it better. The feedback given by users through the feedback service and the answers Q&A gives us a lot of ideas.
But people’s way of work change evolve all the time. With software we should try to foresee changes, and in the case of structuring work, be compatible with new ways of working. Now, project and work management is a field where there is a lot of competing software, and new solutions are created quite often. So in the last weeks I checked competitors for new ideas and evolution that would cover the recent trends in ways of working, like for example having the browser as the “operating system” where more and more applications operate, and so in many organizations a considerable amount of activity is on applications in the browser. Yes, of course Teamwork is web based, but one can do much more than that today. New ways of working need new ideas, sometimes radically new ones. Is anyone proposing different models, or reacting to new working ways?
Well, to my surprise, no. The same mistakes are simply repeated, again and again, like trying to “trap” user communication flows and other user usages in the project / work management software; development is done under wrong beliefs like “using e-mail is wrong, and users should be ‘educated’ to centralized communication systems”. Such tasks are destined to fail: it is simply assumed that users will happily and daily spend a considerable and growing amount of time on your specialized project / work management application because of their stakanovistic dedication to organization, which is the opposite of what is happening: people use more and more different, specialized applications for their tasks, and dislike and refuse single, centralized “monster apps” which attempt to replace all others.
In my review of “solutions” I’ve even seen a specific content manager connected to a popular issue tracking system that offers users a blogging platform. Now, how likely is that? How happy will employees be of being forced to blog in that corner of the bizarre issue tracking software instead of using their preferred blogging platform? This kind of ideas just don’t make sense: you have to improve work management without directly impacting software usage, and without trying to replace high quality specialized solutions with centralized (low quality) ones.
We have learned a minimalistic, relational approach and deposited it in Teamwork years ago. Now what about going beyond that? Well, no concept evolution is happening in direct competitors.
So in my search, I ended looking at personal productivity software, after seeing this nice presentation by Scott Hanselman, and there indeed there are some original ideas; consider for example Evernote ©.
The high level of interactivity, openness to devices and compatibility with user habits of this application is striking. The aim of Evernote seems not as much managing work, as simply collecting notes for personal usage. But there is a lot of stuff to look and learn. And many users will start work management from a personal perspective, and then will try to propose it as a shared approach: I believe this is a path that currently lacks appropriate tool support. There is a divide between project / work management tools and personal productivity ones that should not be there. On one side project / work management tools still pursue the centralized application option, on the other the sharing features of personal productivity tools are weak.
So we decided to open an experimental platform where to try and test different approaches to managing work, in particular starting from the personal / to-do point of view. In the meantime, Teamwork will keep evolving and improving, eventually getting new features and improvements from this experimental platform. We will blog about our experiments here in the coming months. If you any suggestion to make, post it on the feedback service: thanks!
P.S. Teamwork release 4.4 should be out in a couple of weeks (a free upgrade to all users of version 4), and will introduce the notion of “public” project – keep in touch.
Open Lab and Teamwork are not associated with Evernote in any form.
Teamwork release 4.3.14232
This is a minor update but it includes two useful new features, also requested on the feedback service:
- in task list the possibility to filter by the creator of the assignment, and not just by the assignees. This will work for new assignments.
- cookies management to store user’s credential data in the web-browser.
Download the release here. The installer will upgrade your web application; the database schema in this release will be changed (it just adds a new column in “twk_assignment” table).
Other features included:
- added in the RSS reader web part a filter to set the number of feeds shown
And here the bug fixes:
1- Fixed error page in Internet Explorer 7
2- Fixed a bug in the drop down list
3- Fixed a bug in the test connection procedure for Pop3 configuration.
4- Fixed a bug in Internet Explorer 8 opening documents form task
5- Fixed a bug in the copy/move functionality, added a default operation.
This is a free upgrade for all users of version 4.
Teamwork release 4.3.13260
This is a minor release which includes some bug fixes.
The most important one is the one for setting at the first start of the application the correct currency and date format according to the language chosen.
You can download this release here;
This release does not include schema changes.
Teamwork release 4.3.13250
This new release includes some useful new features, the translation in Slovenian, and some bug fixes.
Many of these fixes and features come from Teamwork users who, through our feedback services (answers and new ideas), always help us improving the software, making Teamwork more usable and “comfortable”. In particular we should thanks Marko Vaupotic from the Skrasistemi for the Slovenian translation.
Download this release here; there are no database schema changes from latest release. Technical note: the web.xml of the application will be updated.
Collect errors with BugsVoice:
From this new release Teamwork’s errors are going to be collected using the BugsVoice online service. This will probably not be a big difference for Teamwork users, because the page shown in case of errors is quite the same (the same information with a new skin
), but it is a complete example of BugsVoice usage. Give it a try to trap your errors!
Features:
1. Possibility to notify a user by email once his/her account has been created.
2. In the first step of Teamwork usage, if you chose “software house” as company type, the operational role will be changed adding to it the permission of issue creation (according to how this type of company generally work: everybody can add issues)
3. Possibility for a resource a resource to modify his/her personal data even without the resource_write permission.
4. Added the possibility to choose if drawing or not your sticky notes in case the user has more than 30 when logging in.
5. Added a in the list of subscriptions a new one which alerts if a child task is created.
6. Teamwork scheduler know sends e-mail in a nicer format.
7. Added a smarter link for sending e-mail, if you use Gmail for example the e-mail link redirects you to it.
8. Added the possibility to remove all subscriptions with one click.
9. Added the possibility to customize the text automatically added in the action of the worklog created on issues: If you close an issue the action includes the label “CLOSED_ISSUE_PREFILLED_ACTION” If you simply add worklog on an issue the action includes the label “ISSUE_PREFILLED_ACTION ”
10. Traslation in Slovenian.
Bugs:
1. Fixed bug on combo box in issue editor.
2. Fixed a bug on saving worklog in the issue editor.
3. Fixed bug on search: task with notes and tags were not found searching by something written in a custom filed.
4. Fixed bug on search result: notes, tags an custom filed were shown without spaces.
5. Fixed an inconsistency in the view of costs in the worklog analysis page.
6. Fixed a bug in the report with worklog detail(task name showed twice)
7. Fixed an inconsistency of behaviour in worklog management. Users without permission now cannot change the status of their worklogs.
8. Fixed a bug in the generation of a link-type document.
More questions? More Answers!
Today we put online a new support and Q&A’s site for Teamwork. Here it is:
During this year we focused on improving communication with the Teamwork’s community, by getting more and more contributions from our customers and testers; for this reason we have tried to improve the way people can give us feedback.
UserVoice has been the first service that we have put online to collect your ideas and suggestions for new Teamwork releases. This service has had a great success.
Following this line we have worked to provide our customers a more and more comfortable way for getting support; after considering different hypotheses, we chose the Q&A service above because it is very user friendly and responsive.
The new support service, which uses the same engine as StackOverflow, the popular developer Q&A’s site, is very easy to use and is provided to let you ask questions about Teamwork functionality and about work management in general, and get good quality answers.
So let’s go there and ask!
Everybody contributes!
One of the features appreciated by Teamwork users in contrast with other web applications for project management is that it is not exclusively oriented to technical users. For example, about 8% of Teamwork customers are software houses, and several of them migrated from bug-tracking oriented software to Teamwork, simply by realizing that there is more to software development than just bug tracking.
In order to facilitate usage and group contributions, a trick to enable issue add for everyone in the project area, even if not assigned to projects, is to simply extend the “operational” role, created by default by setup, with the “task read” and “issue create” permissions.
This was suggested by Roberto and closes a feature request here.
Note: the logo on the left is the logo of our “error serving and collecting” new online service which will go in public beta soon: bugsvoice.com.
Teamwork release 4.3.11360
This patch release includes one major extension and one bugfix.
The major extension is the support for PostgreSQL, we have in fact corrected a known error in the Hibernate’s PostgreSQL dialect.
You can read here for more details about this issue.
Bug fix: error in issue multi-line editor, adding a new assignee for the task of the issue.
Download this release here; there are no schema changes from latest release.
Teamwork release 4.3 available for download
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 |
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.
Comments (3)



