[Nicolas Noullet]

Glad to know that it worked! 🙂

[Nicolas Noullet]

First, it is important to understand the model, which is designed in an object oriented fashion. Sprints and releases are represented by the classes Sprint and Release, which both inherit from an abstract class named Timebox, which gives them the startDate and endDate attributes.

In the DB, the Sprint class is represented as the icescrum2_sprint table, the Release class is represented as the icescrum2_release table and the Timebox abstract class is represented as the icescrum2_timebox table.

That means that for every sprint and every release, there is a row in there respective table and another row with the same id in the icescrum2_timebox table that stores its startDate and endDate under the start_date and end_date columns.

First, stop iceScrum and make a DB backup. Then, you will need to update the icescrum2_timebox table for the sprint. I recommend that you also check that the release startDate is correct (a sprint cannot start before the first day of the release). Finally, start iceScrum.

[Nicolas Noullet]

There are two different problems here:

– Updating dates for record keeping purposes

I am sorry but I did not understand your issue. I am not an English native speaker so this may affect my understanding. Could you please rephrase it by providing the current state of the dates and the state you want to reach?

Please note that using the API will not work around business rules enforced in the GUI so if you cannot update a date in the GUI then you will not be able to do so through the API. The only way to bypass the business rules consists in updating the database records manually but this should be avoided as much as possible in order to prevent inconsistencies, instabilities, data loss…

– Updating the sprint start date through the API

The problem here is that you provide a body of Content-Type « application/x-www-form-urlencoded ». The API only accepts JSON and XML formats as output and input. That means that if you provide a body with the request then it must be either in JSON or XML, as explained in the documentation: https://www.icescrum.com/documentation/icescrum-api/#summary_6.

Regarding the date format, as explained in the documentation: https://www.icescrum.com/documentation/icescrum-api/sprint-api/, if your user uses the EN-US locale then the format is MM/dd/yyyy.

Here is an example of cURL command that is more likely to succeed:

curl -X PUT -H "Content-Type: application/json" -u user:pwd -d '{ "sprint": {"startDate": "04/29/2015"} }' http://icescrum.example.com/icescrum/ws/p/INFRA/sprint/1106

[Nicolas Noullet]

Hi,

We do not recommend to follow « manuals » or « tutorials » to install iceScrum because, unfortunately, they are either wrong, incomplete or outdated.

Here is what is needed to install iceScrum:
1. Install a Java, we recommend and support Java 7
2. Install a servlet container, we recommend and support Tomcat 7
3. Install a DBMS (optional but strongly recommended for production purposes).
4. Install and configure (config.groovy) the iceScrum web application, configure the container (server.xml) and the JVM that it uses (CATALINA_OPTS) accordingly, create the empty database if you use a custom DBMS.

Steps 1., 2. and 3 are external to iceScrum and there there is no unique source of truth regarding how you should install these tools: it depends on your OS, your context, your security policy etc. One must understand how they work in order to configure a server properly and safely, and there a plenty of good documentations (starting by the official ones) to get there. As an example, just for Tomcat on Ubuntu, there are several valid ways to install it (command line package manager, GUI package manager, archive), and use it (service or not, specific user or not, use the Tomcat Manager GUI or only config files and command line…).

On the other hand, everything that is specific to iceScrum (step 4.) should be provided in our install guide: https://www.icescrum.com/documentation/install-guide/.

Your error message tells us that iceScrum cannot create the prodDba.properties file because it lacks the necessary permissions. As explained in the documentation, this file is part of the database generated by the default DBMS that comes with iceScrum, and by default these files are created by the user who starts Tomcat in the start path of Tomcat. You can fix this issue by providing the permissions to create this file to the user who starts Tomcat or by configuring a custom DBMS.

[Nicolas Noullet]

Hi,

Thanks for your feedback!

Before trying to address your specific needs, I will answer your more general comments:

You are right, adding columns and making them convenient would require a lot of work. The cost of development is significant in Product Ownership decisions: the Product Owner is likely to prioritize features that add the most value for the minimum cost.

However, the cost of a feature cannot be considered independently: it must be weighted regarding the value it provides. This value is not absolute, it depends on the product vision. As part of our vision, we believe that following agile principles a key success factor. Thus, for us, a feature that encourages that brings much more value than one that can (and will) be misused at the expense of projects success.

Another important thing to consider is complexity (from the user point of view): adding features, even if they are all very valuable and well implemented, can lead to unusable software. Thus, we tend to avoid developing features that have a significant complexity overhead if they can be worked around with existing features.

This makes iceScrum an opinionated tool: toward agile values and toward simplicity. This can take precedence over allowing teams to « decide themselves ». If it was not the case then iceScrum would probably be a mess of configuration (somewhere between Excel and Jira, maybe worse) and would help micro-manage, track individual performance, transform sprint into waterfall…

Regarding your specific issue, if I understand well there are two needs:
– Provide the link to the code review: the notes and the comments are a good place to do so because they offer rich text editing to make links clickable. The notes may be better because they are displayed in the « quick view » (opened by double-click).
– Show that the item is in review. If you do review on whole stories then I would recommend to create a « Review » task so it is made clear when it is to do, in progress or done. If reviews are at the task level then you can use task custom colors to make it visible that the task is in review.

[Nicolas Noullet]

Hello,

As stated in the documentation https://www.icescrum.com/documentation/install-guide/#software-requirements, iceScrum requires requires Java 6/7 and Tomcat6/7.

We are working on Java 8 and Tomcat 8 support, which will be available in the next major version of iceScrum.

[Nicolas Noullet]

Hello Jim,

You spring does not pass business rule validation and this is likely to prevent stories to be marked as Done.

Could you please send me an export of your project? (nnoullet at kagilum dot com)

[Nicolas Noullet]

Bonjour,

Vous pouvez envoyer le projet à nnoullet _ at _ kagilum _ dot _ com

[Nicolas Noullet]

Merci pour vos encouragements !

Nous procèderons bientôt à un rafraichissement des indicateurs dans le cadre de la nouvelle version majeure : iceScrum R7.

Il prendra en compte l’évolution des pratiques, notamment en termes d’estimation. A ce propos, certains recommandent même de ne pas estimer les stories, dans ce cas on aurait plutôt un burndown en nombre de stories. Il pourrait y avoir un burndown en nombre de tâche.

[Nicolas Noullet]

Bonjour,

Le seul indicateur relatif aux stories dans le sprint est le burnup en nombre de stories. Le burndown de stories en points n’est disponible qu’au niveau release / projet, avec comme abscisse les sprints.

[Nicolas Noullet]

Bonjour Cyril,

Certains éléments de documentation sont présentés sous la forme de blog post, c’est le cas de la gestion des droits. Voici le blog post correspondant : https://www.icescrum.com/blog/the-roles-in-icescrum/. Nous travaillons sur un nouveau site web qui présentera ces informations de manière plus claire et unifiée.

En l’occurrence, lorsqu’un StakeHolder est enregistré et connecté dans iceScrum, il a le droit de créer du contenu dans le bac à sable et de le modifier.

[Nicolas Noullet]

Hello Karthik,

You are welcome, I am glad that it worked on time! 🙂

[Nicolas Noullet]

Thanks!

I would recommend to try upgrading again after manually cleaning the installation:
1. Stop the iceScrum Server application (be careful, if you close the window the application keeps running in background, you can kill it in system tray)
2. Delete everything in C:Program Files (x86)KagilumiceScrum Servertomcatwebapps
3. Delete everything in C:Program Files (x86)KagilumiceScrum Servertomcatwork
4. Start iceScrum Server
5. Click on « Download iceScrum » in iceScrum Server
6. When the download has ended, check that C:Program Files (x86)KagilumiceScrum Servertomcatwebapps contains a file named icescrum.war that is approximately 77MB.
7. Start iceScrum in iceScrum Server.

[Nicolas Noullet]

You will find it under the following folder :
C:UsersyourUserNameAppDataLocalKagilumiceScrum Serverlogs

[Nicolas Noullet]

Hello,

Can you please provide the content of icescrum.log?

[Auteur]

Messages