Help get this topic noticed by sharing it on Twitter Twitter, Facebook Facebook, or email.
Caleb Brown EMPLOYEE
Caleb Brown (Official Rep) February 01, 2010 23:41

ScrumWorks Pro 4.3 Change Log

We're excited to announce the release of ScrumWorks Pro 4.3. This post supplements the release notes by providing a detailed list of changes.

4.3 Change Log

  • Tasks can be saved without an estimate. Task estimates are no longer required.

  • Tasks "Done" Sprint Burndown chart. New overlay on the Sprint Burndown Chart tracks the burndown of finished tasks with blue points and lines.

  • Sub-Totals of selected PBIs and/or Tasks in status bar. Users can select single items, multiple items, and headings to see summary effort and count information in the new status bar on the bottom-right. See Topic

  • "Unassigned" in Team Member Load report. Teams can see the outstanding balance of work in a sprint. See Topic

  • Drag target sized increased for sprints. PBIs and Tasks now have a larger drop target, making it easier to move items into Sprints.

  • Team Member Allocation report: simplied the Excel® export's formulas to enhance performance.

  • PBI Key now appears in the PBI editor. See Topic

  • Exclude Themes filter/highlight option. See Topic

  • "Move To Release" context menu action no longer scrolls to new location. In this way, users can move items without having to scroll back to the original location. See Topic

  • Fix for Java Web Start caching issues. Once ScrumWorks Pro 4.3 clients are updated, JWS caching errors should be reduced or eliminated.

  • Fixed Task estimate history issues affecting Sprint Burndown Chart. This corrects problems with tasks carried over from previous sprints affecting the current Sprint Burndown Chart.

  • Fixed issue allowing authentication with empty passwords when allowed by directory authentication. Regardless of directory authentication rules, ScrumWorks Pro Server will reject empty passwords.

  • Fixed sporadic errors related to deleting Program Epics.

  • API: Added support for comments, a feature not yet implemented in the client. Integrations may take advantage of this API-only capability to store comments data.

  • Fixed greyed-out archived releases in the Release Planner.

  • Fixed issues with invalid XML characters in Print to Cards feature.



As always, we're looking for your feedback. We encourage you to leave your comments here or post new topics with ideas or issues.

Happy Scrumming :)
The ScrumWorks Team
Reply