Access Teamwork everywhere: get the mobile module
Teamwork Mobile and 4.7 release
This is an important release and update: Teamwork now has a custom made mobile module that allows to access it using mobile devices like iPhones, Android, Blackberries to read all your Teamwork data online and also to update some of its contents.
The mobile module is an additional module that can be purchased and activated any time – see all details below.
Moreover the core web app has been greatly updated: the 4.7 update is a free update as usual for all users of version 4. Please read the update instructions below.
Teamwork Mobile
Teamwork Mobile is a new interface designed for accessing Teamwork with mobile devices. It allows reading all Teamwork data and insertion/editing of issues, worklogs and events in the agenda.
You won’t need to install anything on your mobile: it is simply HTML5, which also facilitates updates. So if your users use different kinds of mobile devices, say some have iPhones, some Android devices and some Blackberries, all of them can use Teamwork mobile.
The mobile module can be used only if you have a running Teamwork instance updated to 4.7 – it is not a stand-alone application. And your Teamwork must be visible on the web, of course.
What you can do. Access all your Teamwork projects, issues, worklogs, events. Add and close issues, record worklogs, add events. Read documents. And a nice last touch, you can access Teamwork’s file storages, so Teamwork is acting as a gateway for you mobile access to your intranet documents.
Where it works. Teamwork mobile works on the following devices: iPhone 3/4, iPad, and on updated Android and Blackberry (do test your device on the demo).
How to try it. Create a demo account at the usual demo installations:
Then with your mobile device just go to this URL:
http://demous.twproject.com/mobile
or
http://demo.twproject.com/mobile
respectively.
How to buy. The mobile module is not included in your Teamwork 4 license (but the update to 4.7 is), also not included in unlimited users licenses.
The mobile module has a fixed price, 990 Euro per server, 490 Euro if you are using yearly licenses. So you can buy it at a fixed price and use it with all the Teamwork accounts from your Teamwork installation. The mobile license module expires at the same date of your “main license” expiry – so if you have a non expiring license, it never expires.
You buy it here: http://www.twproject.com/licensePrices.page
The license you will receive after purchase (usually within two working days at most) must substitute your existing Teamwork license.
All new demo licenses generated on Teamwork web site include the mobile module.
How to activate. You have to update your Teamwork to 4.7 and buy the extended license. This done, you just have to point your mobile browser to [YOUR TEAMWORK URL]/mobile. So for example if your Teamwork is at
you will need to go to
with your device’ browser.
Teamwork 4.7
This free update contains several major improvements.
Multiple incoming e-mail automatic testing
This feature considerably expands the management possibilities for anyone handling helpdesk like situations. You can now have multiple “background jobs” running in Teamwork that check several e-mail accounts (say, one per main project) and create issues for incoming e-mails.
In the user guide at 5.4.2 Adding issues to tasks XXX this feature is documented in detail.
Updating and refusing appointments
Handling of sync of the agenda through iCal sent via e-mail has been improved:
- If you create an appointment / meeting in Teamwork, those who have activated sync with their e-mail client can now refuse. If they refuse, the creator of the appointment will be notified, both via e-mail and by Teamwork sticky note.
- We also support sending from the client proposals with a new schedule, again the creator of the appointment will be notified, both via e-mail and by Teamwork sticky note (the appointment will remain
unchanged).
- Moreover we made it compatible with refusals also from Google mail /calendar, which uses a completely different format.
Kanban / Organizer view
Now you can add issues directly from the Kanban / organizer view.
Project diary HTML support
The project diary entries now support HTML contents and formatting.
Faster dynamic lookup combos
All dynamic lookup combos e.g. the one for selecting resources when creating assignments respond way faster.
Minor features
- The workflow management part can now be disabled, simplifying the interface.
- Project processes can now be cloned.
- Email password fields as passwords in settings.
- For Pop3 configuration you can set a port on settings.
- Worklog analysis now can filter also by issue.
- Load computation considers the plan for Saturday and Sunday if present.
- Events found from event search can be bulk deleted.
- Plan calculation revised according to “Wouldn’t it be more appropriate to sum the planned hours over the whole task duration and then remove them from the estimated worklog in order to properly calculate the load” – see http://answers.twproject.com/questions/1849/work-load-calculation-and-planning
- On mobile you can add resources via vCard.
- When using LDAP, create user on login, and mixed mode auth ON, login name is disabled on resource editor.
- While creating assignment: once selected a resource (even not saved yet) added a link to operator load.
- Issue list: if task name is big the text for issues is small… –> Fixed.
- Add to options in public task page: remove spam protection (e.g. case of intranet).
- There is a new web part: panic board, to follow closely the progress of a single project.
- There is a task filter in the web part “create issues”.
- Copy task: added property “copy cost” in addition to “copy additional costs”.
Updated the technology
This update also contains a major technological update under the hood. This means for example more compatibility with Microsoft Project © imports, that Teamwork is compatible also with the new Apache Tomcat 7 and more. Also the database resources used by Teamwork have been considerably lowered.
Bug fixes
- In some cases cloning a task did reset on dates.
- Task description is taken from flux definition when defined. (As requested: http://answers.twproject.com/questions/1369/define-task-description-in-flux )
- When creating the event for task expired it creates a wrong path to the task.
- Fixed dynamic combos for IE9.
- Twitter integration libraries updated.
- “By updating to the current teamwork version we just experienced that “”t:”" in the searchbar isn’t working anymore the same way as before… In the past t: searched also in the (code/short name) of a task – now it is only doing it in the (name/description/notes) field?” –> Fixed.
- Issue editor: pm with only operational could not assign a new resource (not already on the task) –> now he/she can.
- Assignee combo in project list: if resource has no name but only surname it can’t find it –> fixed.
- Print pages sometimes print the print menu –> Fixed.
IMPORTANT FOR UPDATING: Remove all Jars from Teamwork’s WEB-INF/lb directory before the update, as most of them have been updated. To empty the “lib” directory you will need to stop Teamwork. So proceed as follows:
1. do complete backups as documented here:
2. stop Teamwork
3. empty the […]WEB-INF/lib directory
4. do the update
5. verify that the […]WEB-INF/lib contains the 83 Jars of the update
6. start teamwork
The update procedure will also update your web.xml file. And finally, if you installing on Oracle, be careful of using the same schema name of the user and writing all in upper case 
.
Teamwork 4.6 released
This release includes several bug fixes, improvements and an exciting new feature.
The exciting feature is that now Teamwork provides a mobile interface to easily add issues on your active projects.
You don’t need to install anything in order to use Teamwork from a mobile device: you just need a browser and being online, your Teamwork has to be accessible /exposed online too.
The mobile application will be available at this address: http://yourTeamworkDomain/mobile
The release includes also some bugfixes:
- Issue portlet bug.
- Worklog action not more truncated to 10 characters in issue editor.
- Document search by type “File Storage”.
- Agenda event send in the ical file if it is private or not.
- Issue editor re-organized to work on lower resolutions.
- Plan by task and plan by resources error fixed.
- Bug fix on resource description overflow.
- Improved search in smart combo for case sensitive database.
- Load details calculation bug fixed
- Bug fixed on worklog management.
- Check missing worklog error fixed.
- Assignment list bug on saving hourly cost.
- Bug on administration page on tab logs.
- When a new issue is created it is saved a log entry in history.
This new release includes an improvements in the operator load view which now shows also the work done each day by users.
A new functionality has been added that lets you easily find all working days when worklogs have exceed a certain amount.
Download this release here; there are no database schema changes from latest release. Technical note: the web.xml of the application will be updated.
Recent progress in Teamwork development – towards 4.6
Well, first of all let me say that Teamwork 4.5 has been a great minor release; I have to call it “minor” as it has been and it is a free upgrade to all users of version 4 even if it was actually a “major” release according to the number of features it introduced.
The long list of functionalities has been highly appreciated by our users and thanks to them and their feedback we are now working to improve some of them.
Thanks to our forum through which we provide free support we are constantly in contact with our users and their problems in managing work giving us the possibility to help them and, at the same time, collect suggestions and bug notifications.
All this feedback is now “put at work”.
Some examples:
- We are improving new editors in place (which replace the pop-up screens) in order to be visible also at lower resolutions.
- We are improving the usability of the operator load and plan, trying to make them more intuitive.
- The new release will have several performance improvements.
This new release is under development so you have time for suggestions or bugs notifications:
http://answers.twproject.com/
Stay tuned.
Teamwork relational structure
Filed under: IT integration, news, technical | Tags: Teamwork relational structure
Comments (3) 
Following some user requests, we’ve put together a first documentation of Teamwork’s relational structure, that will be a part of next release of Teamwork user guide. Here is the PDF. Hope it helps!
P.S. Published an update expansion on July 19 (2010).
How do I begin project management?
Filed under: project management, work management | Tags: project management, work management
Leave a Comment 
In “Making things happen”, the author (Scott Berkun) states that he assumes that the reader is not stupid, is curious and pragmatic, does not like jargon or big theories, and does not take herself, software, or management too seriously. Well, we do the same in Teamwork.
Still, you may have no or little experience in managing team work. Whatever work you will be doing, you may have some requirements, and some dates. if your company has no notion of project / task / issues, you can start this way: list all the things you are doing in your organization. You could separate internal work / external work. In the list obtained, group dependant activities: each group can be called a project, and the people that should work on it are the assignees.
You may notice that when you are listing “thing that we are doing”, you may also include “things we should be doing”. Notice which of these are stated in the form of concrete actions, like “call X”, or “write Y”, and which are still to be transformed in actions. You should try to transform everything into actions, and get rid of the rest. And still among actions there are simple, brief ones, and others that group many others: you could model the simple ones as issues, and the ones comprising others as tasks (that is, projects which are child of other projects). This is a start of management.
Often we get asked by people evaluating Teamwork:
How do companies really use Teamwork?
In the new user guide you will now find several examples. Here are also some good books where to start learning about personal and project management.
Some reference books:
This book by Berkun is our main reference:
Making Things Happen
Mastering Project Management
By Scott Berkun, publisher O’Reilly Media, 2008
http://oreilly.com/catalog/9780596517717
From a personal productivity perspective:
Getting things done
By David Allen
On the Agile/Scrum theme:
Agile Project Management with Scrum
By Ken Schwaber
http://www.amazon.com/Agile-Project-Management-Microsoft-Professional/dp/073561993X
Teamwork 4.5 patch release (4.5.17900)
As always after a major upgrade, thanks to your detailed feedback we can already do a patch release with a few bug fixes. This is a free upgrade for all users of version 4. Get the installer / upgrader here: http://www.twproject.com/download.page
Bug fixes:
- IMPORTANT BUG FIX FOR ORACLE INSTALLATIONS: Release 4.5.17800 had a schema name bug which made it impossible to install it on Oracle – a problem in our Oracle test due to an existing table made us fail to detect the problem. This release works fine on Oracle.
- issue editor is now compatible also with lower screen resolutions
- issue statuses can now de deleted
- the “worklog day” portlet now saves also descriptions
Teamwork 4.5 released: a major free upgrade
Filed under: issue tracking, news, project management, releases, usability, work management | Tags: kanban tool, Teamwork 4.5, teamwork issues
Comments (3) We are really happy to announce this major release update. As you may guess from the length of this announcement, this update will improve your Teamwork in almost every section, providing more modeling tools and functions. The web browsers’ enhanced capacities (in particular those of Firefox, Safari and Chrome) are used in depth to give users a better experience.
This is a free upgrade for all users of version 4. Get the installer / upgrader here: http://www.twproject.com/download.page
The main features of this release are:
- Issue managing by dragging – “kanban” like.
- History of issue assignee, status and task change (better help desk and issue scaling support).
- Customizable issue statuses.
- Better graph and agile / scrum handling.
- Cross links between tasks / issues / resources / agenda events / meetings / boards.
- In-place popup editors.
- Operator load computation has become much smarter.
- Greatly extended user guide with real case work “mappings” to Teamwork, and a new section on performance optimization.
Layout changes
Several pages that up to now were popup windows are now windows in place, which improves their usability: issue editor, custom forms, workgroup selector.
Several text areas now support internal links (e.g. T#MYCODE#), web links (http://www.twproject.com), smiley’s, absolute URLs to images.
New features
Issues.
Issue statuses – customizable. New issues statuses can be created. There is a page for managing issue statuses (which before version 4.5 were fixed):
And for every status not only its color, but most importantly its business logic behavior is determined from this editor:
Whether it should “behave” when asking user feedback as an open status, as close, whether it should ask for comments and / worklog when entering a status.
So typically if your status is something in which the issue enters at “end of life”, it should be marked “as close” and “ask for worklog” too should be enabled.
Issue change history. When changing a status, task or assignee on an issue, the editor will ask for a reason, and the change will be recorded on the issue. And in fact there is an additional tab on the issue editor, “history”.
Issue organizer “Kanban”. Issues can be now be organized in a completely visual way by dragging and dropping them: filter the issues in which you are interested in, and then select the “organizer” button.
Now you can also enable use of external codes on issues (admin -> default for projects).
Dashboards.
The usability of the “customize this page” function has been improved: all portlets are always visible:
And it’s easier to drag them in the dashboard. Moreover it is easier to access the general page / portlet disposition page: just click “all users”. 
There is a new additional starting page: help desk support.
Operator load and planning. This was the user request:
“refine the operator load showing the effective load taking in consideration worklog done. E.g: 100h estimated on 20 days, done 10h in 10 days the resting 10 day must have a load of 90h not 50h like now”
Also take care of unavailability.
Use the new operator load on plan, load by day, end wherever it is meaningful
Operator load textual: put worklog with totals and pink holydays. Use striped background
Advanced users
- The examples in the distribution and the documentation now cover also “custom wizards”: see section 14.4 Custom wizards of the user guide.
Minor improvements
- More kinds of documents are now full-text indexed; these are the extensions now supported:
“.txt”, “.rtf”, ”.log” “.pdf”. “.htm”, “.html”, “.zip”, “.war”, “.jar”, “.xls”, “.xlsx”, “.xltx”, “.xlsEmb”, “.doc”, “.docx”, “.dotx”, “.docEmb”, “.ppt”, “.pptx”, “mpp”, “mpx”, “.msg”, “.msgEmb”, “.vsd”, “.pub”.
Also custom fields are full-text indexed.
Here are several user requests fulfilled:
- “Add worklog approval monthly screen” -> We will add bulk status change in worklog search / analysis (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/305194-add-worklog-approval-monthly-screen?ref=title).
- Expose issue id in editor and list (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/257395-expose-an-issue-id).
- LDAP authentication cascades to system one (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/265843-login-with-ldap-for-external-users).
- Develop a resource snapshot (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/348397-develop-a-resource-snapshot).
- Sort File Storage Document Listing (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/369822-sort-file-storage-document-listing).
- Make “add document content” in a rich text editor (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/239855-make-add-document-content-in-a-rich-text-editor).
- Please put a link to a task on the agenda event (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/223380-please-put-a-link-to-a-task-on-the-agenda-event): we actually did much more by having full internal links.
- Need to add subscription event for when a new version of a document is uploaded (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/624803-need-to-add-subscription-event-for-when-a-new-vers).
- Display agenda items in planByResource like in worklogWeek (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/142356-display-agenda-items-in-planbyresource-like-in-wor).
- Search for specific custom fields.
- You can have a customized help message in the “help” page, just add in the labels CUSTOMIZED_HELP_CONTACT (http://feedback.twproject.com/forums/6995-suggest-features/suggestions/599247-add-a-customizable-area-on-the-help-page-so-local-)
- Notes on issues are on the main tab and self-resize.
- Issue assignee selector got simplified.
- Now you can create subtasks as sub-fluxes.
- Counters can now be reset and deleted.
- When changing a task on an issue, notify the new assignees.
- Since version 4.5 custom fields support also “typing” of data. E.g. “cost,20,java.lang.Double” will add a custom field of length 20 and type “double” (a floating point number).
- Holiday settings: now you have year-specific settings.
- In issue list you can now filter by task type.
- Resource print includes my assignments.
Bug fixes
- Check why in the assignment notification we add a link to the task even if the resource has not the rights to read task … .
- Meetings are not full-indexed.
- Index custom forms data.
- Create issue from task editor menu does not launch creation nor filters???
- Issue multi edit: bulk change gravity do not close actions clicking “close”.
- Fixed MIME for teamworkMenuPlusCss.jsp,
- Issue cloning did not raise events,
- Fixed various combo positions in bulk update screens in case of scroll.
- Summa is not saved on document link and file storage on tasks and resources.
- A fix for Oracle on Resources with no surname.
- An operator may change his own password even if cookies are enabled.
- Do not notify disabled users.
Technical points
- In order to optimize memory usage,
If you log as administrator and go to the label management section, open the “label rules” container (it is closed by default), and say if you want to have only English as language, type EN in the enabled languages field and select SAVE.
- Teamwork 4.5 is no more on quirks mode – we dropped support for Internet Explorer 6 – and pages are in HTML 5
Important for upgrades. Several JARS have been updated, added and removed. If they are present these JARs should be deleted by hand from WEB-INF/lib:
o commons-collections-2.1.1.jar
o commons-logging-1.0.4.jar
o poi-3.0.1-FINAL-20070705.jar
o jcaptcha-all-1.0-RC3.jar
- Added -server configuration to the Java JVM distributed.
- If using HsqlDB you can make a dump of the current log by hand from system check instead of having to wait Teamwork restart:
Notes for updating to 4.5:
Any custom filter on issues will need to be redone as the issue statuses are a lookup field.
Unfortunately all document list attached to discussion points of meetings will be reset.
P.S. We’re building the beta of a new online service – called Licorize – a cocktail of Delicious bookmarking and light to-do management. If you’d like to beta-test it, just send an e-mail to info@twproject.com with “Licorize” in the subject or body – we will soon give you access and also a year of free usage to your entire group.
Stories of work management
Filed under: IT integration, project management, usage, use cases, work management | Tags: management stories
Comments (1) 
In Open Lab we’ve been developing Teamwork and consulting on project and work management software since 2003.
Every time we got in a company with our software, we had planned to show how the software worked, how to optimize its configuration, how to integrate it with existing software. But we actually did so in the last moment of our visit, if ever.
But when we got in we always ended up in meetings after meetings where the topic was not specifics of Teamwork, but questions of work management, and how to best “map and structure” these, so that project trees, sets of issues, workflows and so on could be used in a coherent matter.
And we’ve learned a lot about which mappings work, and which not.
This need for conceptual mappings is teaching something, that is, where is the real value for the customers, what users need.
We progressively realized that the value of software like Teamwork can be simply in the introduction of more structuring, more quality in work. This can be much more than actually using the software – taking it to the extreme, one could simply read this guide, reform practices in the company and forget about the software 
And more people and companies we met, more we appreciated the way we had structured Teamwork from the very beginning to be very, very flexible. A group of fashion designers, a company doing production, a team of software developers, an IT group, hardware engineers, event organizers, all these have different needs. And these groups may be in the same company, and different models need to co-exist.
Meeting diverse needs made Teamwork evolve so that it is an even more powerful mapping tool. Though it is extended, it still is an organically integrated tool.
Modeling company needs for organizing work always implies going beyond the scope of a single application: Teamwork is always used in an applicative context, and so its openness to external integrations is something that in our concrete experience has made a successful adoption possible.
In the user guide for version 4.5 you find also some of our experiences of “map and structure”, some gained by “boot camps” in companies, some by giving web support. You also find the definitions of some concepts related to work management that are not directly linked to software usage.
Some say that all companies need is a to-do list; this is for us just a symptom of scarce experience in what people do at work, of how complex are the needs of a productive company. We hope that the new guide can be of help in understanding which map best fits your organization.
Some of the stories titles:
How do I begin project management?
Managing with lists vs. managing with trees
Overcoming opposition
A critical moment: change
Migrations
Public projects
A design & production company
To Gantt or not to Gantt
Social tools for work management
iPhones for all
A distributed research group
Agile methods
Working by “pomodoros”
Kanban like management
Simplistic cost/benefit evaluations of organizational tools adoption
Worklog validation
Deep IT integration
Work management and games
How Teamwork is made with Teamwork
Teamwork and multilinguism
Business processes
Help desks
Company structure
Different Teamworks, same data bucket
Teamwork and your company’s worth
Lighter, faster Teamwork (release 4.4.16000)
This release (4.4.16000) includes fixes and refinements on memory usage that make Teamwork lighter and faster – thanks to the great Lambda Probe tool for help (we are not associated with them). Both absolute memory usage and memory usage by logged user has been significantly reduced.
A few features included: custom pages can be disabled, possibility to speed up the “my assignments” web part.
The release includes also some bugfixes:
- fix in task list search when you search for code and name
- better logging for scheduler exceptions
- faster task print list
- fixed a rare key incompatibility with certain versions of MySQL
- custom pages can be disabled
- safer schema update procedure
You can download this release here. It is a free upgrade for all users of version 4. This release does not include database schema changes.
A critical moment: choosing or changing a project management tool
Filed under: project management, work management | Tags: reselling Teamwork
Comments (2) Healthy companies, groups which are self-critical tend to periodically reorganize themselves. It is an opportunity to improve both productivity and quality of work. In these moments, software surveys are done to select new software for project and more in general work management. It is in these phases that sometimes Teamwork is chosen. In the choice what most matters is how the software can “unobtrusively” map to the new organizational practices, and Teamwork in this can be great, because of its flexibility, scope, and the wide fit to the IT infrastructure. All this is explained in detail in the user guide.
Now it frequently happens that some software houses (which are about 8% of the companies that use Teamwork) like Teamwork so much that they consider distributing Teamwork themselves to customers, and contact us for that; we always say “fine”, but none has been very successful, and this is quite easily explained: if you have say 20 companies to which you provide software services, what is the chance that that very company will want to buy Teamwork?
About 2% of the companies that visit Teamwork site get to try it; and about 2% of those that try it get to buy it. And consider that all those companies are already in the critical situation of choosing a PM tool. So calling a company at random, what are the chances that they will be searching right then a PM tool? Slim, very slim. And the chances that Teamwork will fit them? 2% of 2%. So how many companies will you have to contact in order to have a good chance of making one sale? Many. Too many.
All this because in this scenario we are not using the power if internet of being found, instead of contacting known ones. If someone wants to offer software like Teamwork to customers, the best idea is to get a good presence on the web, maybe in a localized / specialized part, so that companies in search of PM solutions can get competent help. Just my two cents.
