Archive for the ‘issue tracking’ Category
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 available for download
Filed under: IT integration, issue tracking, news, project management, releases, time recording, work logging, usability | Tags: multi Gantt
Leave a Comment 
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 |
More Teamwork – Twitter integrations
Filed under: IT integration, issue tracking, time recording, work logging | Tags: twitter integration
Comments (1) 
Sending an issue to Twitter.
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.
Teamwork / Twitter integration.
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.
Scrum tools: visually creating Sprints – a mockup
Filed under: issue tracking, project management | Tags: agile, scrum
Comments (2) Following Skype, Twitter and e-mail discussions with Rick Cogley, looking for example at Scrum-ban, we thought about how to improve the current Scrum module, creating a more “visual” interface for creating Sprints. So this is our first mockup of the new “create sprint” page:
Teamwork visual Sprint creation page- first update
Now if you have a suggestion for this interface, just download the mock-up here, modify it and publish the link on our UserVoice or send it back to me (ppolsinelli at open – lab dot com).
Teamwork is (fortunately) not just a specific Scrum tool, in fact in the same company different methodologies may be used in different projects; sometimes only some parts of a methodology may be used. For example, in Open Lab we use pair programming and short cycles, taken from XP, but we do not use test-first coding; Teamwork is flexible enough to adapt to all these, so that you may use a single tool to manage differently structured projects.
First update. Received a mock-up with suggestions from Mr. Cogley:
Cogley update #1
adopted all, apart from “info on tasks” as left side is a single backlog hence from a single task. Thanks!
