Release #15 published on February 25, 2010. Previous release (#14.2) was published on November 13, 2009.

There are a few recommandations about the database you should read before upgrading. Please refer to the « Korean and German localization » part of the news for more details.

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.2 release, the bugs fixes and the known issues of the #15 version.

New stories

357: More action available on table view. On table view mode in the product backlog, it is now possible to select a line and edit or delete the corresponding story without having to switch to « note view ».

351: Velocity chart. The first point in the velocity chart was wrong.

345: Velocity and Capacity (vocabulary). « Planned velocity » or « estimated velocity » is now named « Capacity ». « Real velocity » is now simply named « Velocity ».

299 & 402: Drag&Drop glitch in Sprint Backlog on IE8/Chrome. There were a glitch in IE8 and Chrome making the drag&drop difficult to use in the Sprint backlog.

372: Product Parking lot. This chart is now accessible from the Roadmap view (it was only available in the Product view).

95: Enhanced Burndow Chart. The sprint Burndown Chart now displays every days in the sprint on its X axis.

174: Previous link on charts views. Added a link on every charts views allowing to switch back to the previous opened page easily.

334: Sprint Burnup Chart (tasks). A new chart comparing the total number of tasks in a sprint with the number of tasks done every days. Accessible in the Sprint Backlog charts lists.

74: Demonstration video in french. Available here.

367: « Split » to « Duplicate ». In the Product Backlog, the action « Split » has been renamed to « Duplicate ».

177: Edit a story in the Sprint Backlog. It is now possible to edit a story directly from the Sprint Backlog.

112: Hide week-ends on the Sprint Burnup. A button in the Sprint Burnup Chart (tasks) allows a user to remove the week-end’s data from the graph.

93: Finish definition for each sprint. A view similar to the Vision has been added to store the finish definition for each sprint.

401: Sort columns in the Sprint Backlog on table view. Fixed a bug with the column’s sorting in the Sprint Backlog on table view.

242: Loading a existing project. When trying to load a project that already exists, the import is rejected with a more explicit message.

450: English subtitles for the demonstration video. Added english subtitles on the demonstration video.

400: Change sprint’s starting date. There were a refreshing issue when changing the starting date of a sprint.

385: Starting date of a new release in the Roadmap. When creating a new release, the starting date of the release would always take the ending date of the previous release even if the user set another date. This issue is now fixed.

441: Stakeholder rights evolution. The way Stakeholders are managed has been changed: When a project is closed to new team members, one can still join the project as a Stakeholder, but won’t be able to change his role even if the « Role change » feature is enabled.

347: Copy the previous Finish definition for a sprint. A button allows to copy the finish definition of the previous sprint.

96: Search in the Product Backlog. A new feature allowing anyone to search peculiar stories in the Product Backlog with keyword.

443: Mask a project. The ScrumMaster can now hide a project. An hidden project will no longer show up in the projects list to users that are not members of the project.

507: Collect resources for each sprint. A ScrumMaster can specify the resources used for each sprint.

374: Auto-focus on a rich-text form. When a rich-text form where available, the focus where automatically set on the form after a few secondes after loading the page.  This is no longer occuring.

504: Context menu alternative. The context menus which were only accessible by right clicking on the post-it noteshave been replaced with an embedded menu on each post-it notes. The menu show up on right click or when the mouse is moved over the menu’s icon.

84: Scrum role change. A Product Owner can now switch role directly to Member or Stakeholder. The page allowing to change one’s role has also been enhanced.

Other bugfixes or evolutions

• Fixed bug : Project deletion not working as expected.
• Evolution : Added the test identifiers in the PDF export.
• Evolution : The layout of the PDF export has been enhanced.
• Evolution : Added Korean and German localization.
• Evolution : The bundle version has been optimized for production.

Known issues

• 354: password are not encoded in http transfert. Workaround: use the ssl protocol on your server.
• 83: there are still loss of right click. Can occuring after some specific actions. Workaround: Refresh the page, or disconnect/reconnect.
• 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. The language should be restored to the right one when browsing in the application.
• 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).
• 444: Chrome scroll issue. On Chrome, when there are a lot of projects in the projects list, the list automatically scroll up when trying to select a project, making it impossible to open a project located at the bottom of the list.
• 561: Dissociate a story from a sprint. When a story not finished is dissociate from a sprint, all its tasks (finished or not) are also dissociated. This can be disturbing and it affects the Sprint Burnup Chart.
• 510 : IceScrum² is not compatible with an Oracle DBMS (column’s names length > 30 characters)
• New user stories do not appear in the product backlog, we have to close/reopen the backlog to see the new stories. Workaround : manually select the filter « To prioritize » in the filters list, and check that you don’t have anything in the search box.