iceScrum | Known problems with the R4#4 – iceScrum

iceScrum Blog Get news from iceScrum Team about Agility, Scrum

Known problems with the R4#4

March 19, 2012

 

  1. When iceScrum is installed in Tomcat and the server is stopped, it is possible that the Java process keeps running, which prevents installing a new version of iceScrum. First the process must be killed (on Linux and Mac, with the command ps -ax to retrieve the process identifier then a kill -1 with this number), then the icescrum directory removed from Webapps, the new war installed and then Tomcat restarted.
  2. When changing a feature colour, this is not always changed on stories.
  3. Operation on tablets and smartphones is not optimized.
  4. If the server is setup with a proxy, sometimes file attachment does not work if filenames contain special characters.
  5. In the wizard, an error is produced if the role of the project creator is changed to developer.
  6. The post-it colour in the form for creating features is not reinitialised when several are created in a row.
  7. When the last task in a story becomes done, and the preferences indicate that the story state should indeed  become done, the page must be reloaded in order to see that this is the case.
  8. The number of hours remaining in the sprint is not displayed in the title bar of the sprint plan table view.
  9. When updating a feature in the table view, “NaN” is displayed instead of the correct value.
  10. An export having stories with acceptance tests in its sprints can’t be imported.
  11. Using IE8 (and former versions), the login page redirects to an error page (the login operation works but the redirection fails).
  12. Search on ID (stories, features) returns results that don’t match with the ID.
  13. Stories’ IDs displayed in the sprint plan’s table view are wrong.
  14. The hidden menus dropdown list sometimes disappears.
  15. Manual sprint creation doesn’t work.
  16. Activities related to tasks aren’t displayed correctly in the Dashboard.
  17. Menus which are hidden when resizing the window aren’t restored when the window is resized again.
  18. Wrong ranks in the backlog after story planning/dissociation.
  19. When changing the estimation of a story planned in a “Todo” sprint, the sprint’s capacity isn’t updated.
  20. When a team member creates a comment or an acceptance test on a story, they are published to users browsing the details view of other stories.

If you find other problems with this version, please add them to the  iceScrum sandbox.

 

Published in

  • Kagilum
    About the Author:

Leave a Reply

Your email address will not be published. Required fields are marked *