[Nicolas Noullet]

Glad to know that you managed to find a solution 🙂

[Nicolas Noullet]

Hi,

I have edited your message to hide the URL of your server.

The problem comes from
uri = URI.parse(mycompany.ca)

Here mycompany.ca is not surrounded by quotes so it is taken as an identifier and there is nothing named « mycompany » in the scope of your program.

You should probably write something like (including the port, replace « mycompany » by the proper domain)
uri = URI.parse("mycompany.ca:8080")

Also, you should define the variable username and password with the credentials of a user who have access to the sprint.

Finally, there is no « total » entry in the response body. I recommend that you first try to query the iceScrum API manually: https://www.icescrum.com/documentation/sprint-api/#sprint-api_3, e.g. with cURL, and inspect the response data to know what information you should look for in your ruby program.

[Nicolas Noullet]

Hello,

Glad to know that you managed to solve your issue, thanks for the updates. We investigate to understand how such inconsistency has been made possible.

However, (I say that mostly for other people that may read this post), please note that relying on manual DB updates must be done as a last resort and after a DB backup to avoid losing data / breaking your database.

[Nicolas Noullet]

Hello,

This looks like a bug, thanks for the report we will try to reproduce it.

In the meantime you can define manually the availabilities to 0 (do it on the first cell then you can expand the value to the next cells as you would do in Excel).

By the way, we recommend that you upgrade (https://www.icescrum.com/documentation/upgrade-guide/) to the latest version (R6#14.8 : https://www.icescrum.com/blog/version-r614/) to benefit from all the features and bug fixes.

[Nicolas Noullet]

Hello,

Accepting stories into the backlog is a business decision that is why it is restricted to Product Owners. By the way, the PO can also use the lasso to select multiple stories. Someone who is not PO cannot accept them whatsoever, even by drag’n drop. Here is the documentation for the roles: https://www.icescrum.com/documentation/roles-teams-projects/#roles

PO is not just a « label » chosen randomly as you suggest, it’s access control, a thing that you will find in almost any advanced application.

We chose to offer a restricted number of roles that embody the main distinct responsibilities that you can find in an agile project: team organization (SM), business decisions (PO), work (team members).

We prefer this approach to a fine-grained permission control that ressembles micro-management and that would be contrary to the assumption that team members are collectively responsible for their fate and should trust each other (which is essential for the project to succeeds).

This assumption is also why we offer a role with full permissions: PO&SM, which you may use in your small team where the distinction between roles is apparently not relevant.

While we cannot get rid of access control entirely, this offers the best of the two worlds: truly agile teams can forget about permissions and grand everybody the PO&SM role, other teams can still get relevant restrictions/permissions with the other roles.

[Nicolas Noullet]

Hi Pedro,

Teams often create and estimate tasks at once before activating the sprint, during the sprint planning meeting. In this case, iceScrum can compute the « ideal » median line: a simple downward line from the initial estimate to 0. The first point captures the total estimate when the sprint is activated. By contrast, the remaining time first point is the total remaining time at the end of the day of the sprint activation.

The median line makes sense only if the total task estimate is intended to decrease regularly during the sprint from this initial value. If tasks are not estimated all at once then iceScrum has no way to guess what should be the ideal curve and the median line becomes irrelevant so you can hide it by clicking on the « Median line » label in the caption. The line will not be displayed at all if there is not task estimate when the sprint is activated.

We recommend that either all tasks are estimated before sprint activation (of course the team may forget one or two tasks and create / estimate them later on) or no task is estimated before sprint activation, thus ensuring that the line is displayed only when it is meaningful.

Nicolas

[Nicolas Noullet]

Hello Stefan,

Do you see the « delete » button or menu? If it is the case then what happens when you use it? Is there any error message?

[Nicolas Noullet]

Fred,

Merci pour votre réponse et pour votre enthousiasme ! 🙂

Passez de bonnes fêtes également,

Nicolas

[Nicolas Noullet]

Given what I understood of your context, you already have a Tomcat server but you don’t want the iceScrum installation to interfere with your other webapps (e.g. through the modification of the Tomcat classpath by removing the tomcat-jdbc jar).

That leaves you with two options:

• Deploy another Tomcat server that will be dedicated to iceScrum. It requires having knowledge in Tomcat and following the dedicated documentation: https://www.icescrum.com/documentation/application-server/. The benefit of using your Tomcat installation is that you have full control on it

.

• Use icescrum.jar by following the install guide: https://www.icescrum.com/documentation/install-guide/. It requires very little knowledge and time to install but it will give you less « application server-ish » configuration options. Mainly, it is not possible to use it in combination with a reverse proxy, which doesn’t prevent your from defining custom port/host but will significantly reduce your options

[Nicolas Noullet]

Hello Fred,

The icescrum.jar release replaces icescrum.war + tomcat entirely.

Indeed, the command you have tried is not intended to deploy iceScrum to an existing Tomcat installed on your machine but it rather starts a Tomcat instance that is embedded in the .jar without exposing it to the outer world.

The command output should tell you more about how the deployment goes and it should offer you to open an URL (usually constructed from your internal IP address).

[Nicolas Noullet]

Bonjour,

Changer le lien story-projet dans la table des stories provoquera des bugs dans l’application, il faut donc absolument éviter cette approche.

Il n’est pas possible de déplacer une story dans la version gratuite, en revanche une license iceScrum Pro donne la possibilité de copier une story d’un projet à un autre quand on est Product Owner des deux projets. Il suffit alors de supprimer la story initiale pour obtenir le déplacement souhaité.

Si vous n’avez pas de license iceScrum Pro, vous pouvez en demander une d’essai gratuite 14j. A l’issue de la période d’essai, vous retrouverez les fonctionnalités de la version gratuite.

[Nicolas Noullet]

We look forward to hearing from you then ! 🙂

[Nicolas Noullet]

Hello,

You should have received an email for a follow up!

[Nicolas Noullet]

Hello,

As explained in the documentation (https://www.icescrum.com/documentation/application-server/#application-server_4), I assume that you get this error because you have not deleted the tomcat-jdbc.jar library from the Tomcat lib directory.

Can you try deleting it and starting iceScrum again?

[Nicolas Noullet]

Hello Mike,

The problem is not solved in the latest public release (R6#14.7) and unfortunately there is no easy way to change it.

Thanks for the report, it will be fixed in the next release.

[Auteur]

Messages