Release 14.2 published:  November 13, 2009. Previous release: August 4, 2009.

If you were using a 14.x version before, you don’t have to reset your existing database in order to upgrade your IceScrum.

The numbers preceding each line represent the stories identifiers in IceScrum’s product backlog (managed with IceScrum²). We have listed the new stories done since the 14.1 version, the bugs fixes and the known issues of the 14.2

New stories

• 114 : Installation guide in english. See http://www.icescrum.org/index.php/frequently-asked-questions/about-installation/.
• 87 : PDF export of tasks. There was a shift between owner/creator/state in the tasks list. Fixed.
• 107 : remember me. Allows to reconnect on the last open project.
• 106 : role autocompletion with story template. Custom roles are used for filling the « as » item in the product backlog.
• 105 : vision in the release plan. Rich editor accessible by the eye icon.
• 73 : disable tooltip on expanded post-it notes. After extending a post-it by clicking on the upper left corner, the misplaced tooltip won’t show up.
• 173 : filters for the table view of the sprint backlog. Filters now work in the table view
• 176 : Sonar installed. Sonar is a tool for analyzing code quality and producing dashboard (http://sonar.codehaus.org). IceScrum dashboard : http://outils.icescrum.org/sonar.
• 86 : improvement of the task virtual board display. New dynamic management of tasks in the sprint backlog (mostly visible at fullscreen).
• 76 : Deletion of a sprint. The message was wrong when trying to delete a sprint that wasn’t the last sprint. Fixed.
• 77 : Confirmation when closing a sprint. When closing a sprint, a window will now show up if there are still unfinished stories in the sprint, and will ask for a confirmation.

Other bugs fixed

• Fixed bug: Change sprint dates provokes wrong display.
• Fixed bug: Users can be duplicated in the Online Users display.
• Evolution: The Product Owner can create a build.
• Fixed bug: wrong display of new chat-message notice.
• Fixed bug: wrong display of releases overlapping two years in the roadmap.
• Evolution: Post-it notes contents are now truncated if too long.
• Evolution: Parsed html tags in table views.
• Evolution: Tables headers no longer display a blue bar when they are too big.
• Fixed bug: In an exported PDF, custom roles attributes where showing numbers instead of text.

Known issues in 14.2

• 354 : password not encoded in http transfert.
• 80 : after modifying an accepted story, it gets back to the identified state.
• 83 : there are still loss of right click.
• 349 : moving a story from a sprint to another sprint in the Release Plan is sometimes impossible. Workaround: scale down window display (CTRL – in Firefox).
• 90 : display not refreshed in the Features table when a story is associated or dissociated . Workaround : disconnect and connect again.
• 91 : wrong change of the language after a Scrum role change or when refreshing the page.
• 355 : modification of administration settings does not apply automatically. You have to restart the server manually.
• 352 : cumbersome tooltips. Sometimes, the tooltips won’t disappear. Workaround: refresh the page (F5).
• 299 : defects with some browsers. Workaround: using Firefox.

Recently added :

• In the Tests category, the dropping area for the post-it notes has been reduced to a small horizontal bar.
• 385 : start date of a release. The start date of a new release is replaced by the end date of a previous release.
• 399 : stories modifications not reflected properly. When a planned story is modified, the modifications are sometimes not reflected everywhere it appears (release plan & sprint backlog). The user have to disconnect/reconnect to see the updated values.
• 400 : start date of a sprint not refreshed properly. When the start date of a sprint is modified, the release plan will keep the old data. The user have to disconnect/reconnect to see the updated value.
• 401 : server internal error when trying to sort on the « Remaining time » in the sprint backlog. In the table view, if there is at least one task with no estimation, a sort on the « Remaining time » column will provoke an error.