Archive for the ‘news’ Category
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).
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.
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.
Teamwork in Chinese – 中文 (release 4.4.15200)
Filed under: news, releases | Tags: iphone agenda, iphone calendar synch, teamwork chinese
Leave a Comment This new Teamwork release includes the Chinese translation of the entire interface, we want to thanks Mr. Chenfan for his great work ( we hope that the blog’s title is correct 
) .
This release includes also an improvement in the public task page. We added a new check box that enables showing also custom fields contextually with the “add proposal” functionality. Thanks to this, your customers could send you not only a simple issue with a description but also some additional data from fields that you defined. On issues you can add up to six custom fields.
A requested feature was to display also event hours in the results of the search events page, and its done.
The release includes also some bugfixes:
- bug fix in the project summary web part.
- bug fix in the generated iCal file from the Teamwork agenda
You can download this release here;
This release does not include schema changes.
Teamwork 4.4.0 available: public pages for tasks
Filed under: news, releases | Tags: sharing project data, teamwork public projects
Leave a Comment 
Teamwork 4.4.0 is released: download it here.
We often get requests from customers and evaluators to give access to some Teamwork data to someone who does not log in Teamwork; data like status, progress and open issues on a project . Before this release, to do this you had two options:
1. set the customer as an assignee and give them access to Teamwork with limited rights (which from a Project Management perspective is formally the right choice), or
2. you exported the project data in say a PDF and sent it to the customer
Both choices have their disadvantages: the first one, that you are giving access to a system of which the customer does not know anything about, and the second one is that you have to do the procedure by hand.
Hence in this release (4.4.0) we added a third option:
3. public project pages: for any project / task, a public page can be enabled which will be exposed at Teamwork’s address, will not require login, and will present selected information. It is a way to automate distribution of information always updated from Teamwork to people that do not access it.
The pages will be available at URL of the form
[http://your teamwork address]/project/[task id]
When enabling such pages, there are several options available; most are self explanatory, like “show issues” or “show costs”, but these two need some clarification:
- “enable add proposal”: if you enable this option, visitors to the page will be able to propose issues / features on such task: the proposal will be saved as an open, unassigned issue on the task.
- “ask key to access the page”: access to the page will be protected by a key which you define and will be requested on access.
In the picture above an example resulting page.
Another nice feature is the introduction of custom types on issues (six fields like in tasks) and the refinement of those on tasks, that now support dimensioning. Full details are in the user guide, section 5.8.
Other new features
• added custom prefix for Teamwork notification by e-mail
• issue list export in Excel now exports also estimated duration, so you can esteem the load of any group of issues
• new custom field management with filed size
• added notification on change assignee on issue
• check on issue editor remove tab notes as button submit
• created a new line in notes when the issue change assignee
• nicer browser history
• older hits get removed from database
• tested file storage with Drop Box works just fine
• automated worklog entry question also for issues going from test to closed
• updated Twitter import with latest Twitter4J API
Bugs
• bug on first access with cookies in page size
• fixed bug on priority color in portlet “My assignments” (wp_myAssignment.jsp)
• check on issue editor remove tab notes as button submit
• fixed bug on cookies
• fixed bug on work load
• fixed bug on bulk issue move operations of required fields
• fixed bug on issue list drag and drop
• false JS error message “element not…”
Update
The schema update will add six columns on issues (twk_issues) for the custom fields and the distributed web xml will add a filter for the public task pages.
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.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!
