iceScrum | Version R6#11 – iceScrum

iceScrum Blog Get news from iceScrum Team about Agility, Scrum

Version R6#11

December 11, 2013

Hello everybody,

Here comes a new version of iceScrum and iceScrum Pro!

This version should improve your experience thanks to several bug fixes and UI/UX improvements.

R6#11 – R6 – Sprint 11 (25/10/2013 – 06/12/2013)

New features and improvements

According to the transparency agile principle, iceScrum projects are public by default. However, your projects often carry sensible data so you may want to make new projects private by default. This is now possible thanks to a new configuration entry (available both in config.groovy and iceScrum Pro Administration).

New story template

Story template integration was not consistent. In order to improve that, we looked at how this feature was used and we noticed that story templates were mostly a replacement for the description when users wanted more structuring. To prevent redundancy and make story structuring easier, we now bring the template structure directly into the description (in plain text).

When creating a story, the description field is now pre-filled with the story template (“As a… I want to… In order to”). This feature encourages the use of the story template, that we believe helps write better stories. However, the whole template is selected on the first click so if you don’t want to use it, just start typing as usual and the template text will be replaced by what you type.

Former story template migration

Former template fields are removed from iceScrum. As a consequence, old templates from existing or imported projects will be migrated (appended) into the story description (or in the notes if they don’t fit).

If neither the description nor the notes can handle them, which is very unlikely to happen, then they will be written into the logs of your server so you don’t lose them. However, as usual, we strongly recommend that you back up all your data before upgrading.

Actor autocompletion

The former “As a” template allowed linking an actor to the story. This is still possible thanks to a new autocomplete feature. When you type “a” anywhere in the story description, you can now choose an actor from the ones defined in your project.

Autocompleted actors are inserted with a dedicated markup that allows iceScrum to recognize them,
e.g. A[5-Administrator]. Only the right hand-side text is displayed in post-its and reports, while the left hand-side is the ID of the actor to link to the story. Please note that only one actor can be associated to the story so if more than one actor markup is found, only the first actor is linked to the story.

When creating an acceptance test, it is now pre-filled with the well-known “Given… When… Then” BDD template (highlighted with our markup language). This feature encourages the use of the BDD template, that we believe helps write better acceptance tests. However, the whole template is selected on the first click so if you don’t want to use it, just start typing as usual and the template text will be replaced by what you type.

  • ICESCRUM-532 – Move a story from the backlog to the sandbox

Accepting a story is an important decision that must be taken conscientiously. However, even the Product Owner can make mistakes so it is now possible to move a story from the backlog back to the sandbox.

  • ICESCRUM-600 – UI components upgrade for better accessibility and nicer UI (…and it’s just the beginning :-))

We upgraded to the latest version of the UI components we use in order to bring iceScrum closer to the standards that make the web a better place. Also, select and multi-select drop-downs are more consistent with the iceScrum UI and now offer a search field when their content exceeds five elements.

Bug fixes

  • ICESCRUM-633 – Some story dependencies aren’t imported
  • ICESCRUM-635 – Sometimes, activities aren’t imported
  • ICESCRUM-767 – Project export drops task comments
  • ICESCRUM-829 – Switch user in task board doesn’t work with LDAP users (iceScrum Pro)
  • ICESCRUM-800 – Bug in task board when hiding/showing done work (iceScrum Pro)
  • ICESCRUM-830 – Unwanted switch back to Scrum Master in Task Board (iceScrum Pro)
  • ICESCRUM-765 – Ex members don’t appear in finder creator dropdown
  • ICESCRUM-831 – Quirks mode is enabled by default in modern IEs and prevents from using iceScrum
  • ICESCRUM-597 – Overlapping release name prevents from using release menu in the timeline
  • ICESCRUM-599 – Shift to next sprint inter-release requires at least two sprints in the next release
  • ICESCRUM-812 – “Show more” isn’t displayed in the project list if the user is part of exactly 10 projects
  • ICESCRUM-791 – Bugs when the admin uses project bundle (iceScrum Pro)
  • ICESCRUM-775 – Impossible to delete a project that belongs to a bundle (iceScrum Pro)
  • ICESCRUM-808 – Hitting enter on team form displays team leave confirmation
  • ICESCRUM-818 – Project charts aren’t updated
  • ICESCRUM-792 – User profiles can’t be opened from the project admin
  • ICESCRUM-826 – Initial time is gone when task moved from Todo to Done directly.
  • ICESCRUM-782 – Error when last task is done and AT of parent story not success
  • ICESCRUM-699 – Errors when starting iceScrum with Oracle (iceScrum Pro)
  • ICESCRUM-833 – Commit to a done task with 0 remaining time in the commit message moves the task to “in progress” (iceScrum Pro)
  • ICESCRUM-794 – FullScreen API doesn’t work on Safari
  • ICESCRUM-801 – User profile dead links for stories from other projects
  • ICESCRUM-793 – Autocomplete on actors doesn’t work anymore
  • ICESCRUM-795 – Notifications are mixed under the same Gmail thread

Published in

  • Kagilum
    About the Author:

Leave a Reply

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