[Nicolas Noullet]

Hello,

This is in our plans! Java 8 will be supported by the next major version of iceScrum (R7), which released date is not defined yet.

[Nicolas Noullet]

Nightly backup is a very good policy: there are never two much backups!

Restoring a former database should work like a charm. However, as a general rule of thumb, recovery solutions should always be tested on a regular basis.

[Nicolas Noullet]

Indeed, it is now available thanks to our sponsoring services.

The documentation has been updated accordingly, but if any question remains unanswered, we would be glad to help!

[Nicolas Noullet]

Merci pour vos retours et content que le problème soit résolu.

Il était probablement dû au repertoire work qui contient les resources statiques d’iceScrum, notamment les fichiers JavaScript.

[Nicolas Noullet]

Thanks for your help Michael, it is nice to see someone else than me answering questions here!

However, I think that Gebru13 was asking for a way to list the stories included in a version deployed in the middle of a sprint.

There are two approaches to this problem :

1. Managing the version history manually. You can save the work done at a given point in the sprint by doing a snapshot of the sprint notes (sprint toolbar > documents > sprint notes). You can do so each time a version is deployed to list the content of the version.

2. Doing that automatically. To do so, iceScrum needs to be linked to the tool that builds/deploys the versions. We have developed an integration with the most popular Java (& more) Continuous Integration server: Jenkins. This integration is available in iceScrum Pro: https://www.icescrum.com/documentation/icescrum-pro/continuous-integration/. The content of the latest build can be displayed on the dashboard. Unfortunately, there is no dedicated page for each build so if you want to list the content of an oldest build then you will need to find a story that is present in this build and display its details.

[Nicolas Noullet]

C’est très étrange. Pour avoir installé iceScrum des dizaines (voire centaines) de fois, cette erreur est normalement liée au .jar tomcat-jdbc.

Pouvez-vous essayer de déplacer temporairement le jar tomcat-dbcp dans un autre dossier et redémarrer ?

[Nicolas Noullet]

This error message doesn’t tell much about the problem.

Can you check if you have other errors logged in icescrum.log and catalina.out?

Are you sure that Java 7 is used?

[Nicolas Noullet]

Hello,

There was two problems:
– The Accept header was set but the Content-Type one was required. This one is very strange because the library we use should treat the Accept and the Content-Type headers in the same way (which is not a good thing, but as far as I know it was enforced). I must give another look at this problem.
– The id of sub-resources must be included as attributes
The documentation was wrong about that so we have fixed it.

Here is an example of a working curl command that creates a task :

curl -H "Content-Type: application/xml" -u user:password -k --request POST --verbose http://xxxxxxxx/icescrum/ws/p/PKEY/task -d "CLAIM TASK"

[Nicolas Noullet]

Hello,

You are right, thanks for your feedback. We may include the fix in the next release.

[Nicolas Noullet]

Merci pour ces précisions, tant que c’est de la lecture seule ça ne devrait pas poser de problème.

Vous avez raison concernant le ace_order mais vous pouvez ignorer les masques à 16. En effet, les masques à 1 et 2 suffisent à déterminer tous les rôles Scrum :

ACL de projet :
– 1 : StakeHolder
– 2 : Product Owner

ACL d’équipe :
– 1 : Team Member
– 2 : Scrum Master

Il existe un dernier rôle, le « owner », que vous devriez pouvoir retrouver facilement via la colonne dédiée. Le « owner » affiché dans la vue équipe d’iceScrum est celui du projet (celui de l’équipe n’est pas utilisé).

[Nicolas Noullet]

Bonjour,

En quoi ces informations peuvent-elles vous aider ?

Je pose la question car il faudrait, autant que possible, ne pas se reposer sur ces détails d’implémentation.

[Nicolas Noullet]

Thanks for your feedback, glad to know that it works 🙂

[Nicolas Noullet]

Hi,

We have recently added a checklist to the troubleshooting section of the iceScrum Server documentation. Can you answer the checklist questions here?

Here is the link:
https://www.icescrum.com/fr/documentation/icescrum-server/#troubleshooting

[Nicolas Noullet]

Effectivement c’est le dernier log qui semble indiquer le problème. Vous utilisez Tomcat 7, avez-vous suivi cette instruction dans la doc ?

Tomcat 7 (7.0.23 or greater), recommended: you need to remove the tomcatDir/lib/tomcat-jdbc.jar library.

[Nicolas Noullet]

1. This is not possible, but easy to work around by creating a release that lasts enough to contain all your sprints. Releases carry the vision for a consistent set of features that will be provided by a major version of the product. Nothing prevent to build and deliver versions more often than that: every sprint, every day, or several times a day.

2. In a single iceScrum project, this is not possible. Can you elaborate on why you need this feature?

iceScrum follows the rhythm of Scrum so the planning is tied to a sequence of iterations materialized by sprints. I think that managing continuous deployment and continuous delivery with Scrum is a methodological issue rather than a tool one. You can get rid of sprints in iceScrum the same way you can work around releases: just create a single sprint that lasts several months.

[Auteur]

Messages