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
– Expose issue id in editor and list.
– LDAP authentication cascades to system one.
– Develop a resource snapshot.
– Sort File Storage Document Listing.
– Make “add document content” in a rich text editor.
– 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.
– Display agenda items in planByResource like in worklogWeek.
– Search for specific custom fields.
– You can have a customized help message in the “help” page, just add in the labels CUSTOMIZED_HELP_CONTACT.
– 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.
Nella release 4.4, il carico degli operatori poteva essere gestito anche da piano. Dopo l’aggiornamento il carico da piano sembra non più gestito, esiste qualche parametro per ripristinare questa funzionalità?
Grazie 1000, Alberto
You may find interesting these answers on our forum about this topic:
http://answers.twproject.com/questions/762/teamwork-45-difference-in-estimated-worklog-management#763
http://answers.twproject.com/questions/778/what-does-the-hours-entered-in-the-ressource-plan-represent