[Nicolas Noullet]

There is a new version of iceScrum : 7.1.0, you may try with its war to see if the problem persists (https://www.icescrum.com/download/v7-0-war/).

Are you sure that you checked both log files: catalina.out (server standard / error output) and icescrum.log ? It’s really strange that the error is not visible there.

Without an error message it is really hard to troubleshoot…

[Nicolas Noullet]

Yes you can send only the XML.

If there is no such inconsistent Task in the original DB then the inconsistency may come from the XML or the import process (e.g. a task that would be attempted to validate before it is fully populated). Thus, I am afraid that no SQL query could help with that.

[Nicolas Noullet]

This is not a stupid question at all, it’s our bad. Sorry we missed the Docker part in your previous post, as stated in the iceScrum Docker documentation:

There is no https support for the moment for this Docker image.

If you really need to use iceScrum with HTTPS now, the best way to go is to install Tomcat manually on a server, then put scheme= »https » in the connector part of the Tomcat server.xml file.

The documentation explaining how to install iceScrum with Tomcat is not fully up to date with iceScrum v7 but you can use it as a reference: https://www.icescrum.com/documentation/application-server/.

[Nicolas Noullet]

Hi,

Thanks for your suggestion, that’s a good idea and as you said, technically this is very minor.

However, that does not mean that it is easy to add in iceScrum. Indeed, we cannot add small features everywhere, even if useful and not complex. They would pile up and result in a cluttured UI without consistency that would provide a terrible user experience. Actually, we are still working on improving the current UX since the new UI is only a few months old.

We did not manage to find a nice way to integrate your idea into iceScrum yet, but we took good note of it!

[Nicolas Noullet]

Bonjour Erik,

Comme indiqué dans la popup de confirmation qui s’ouvre lors d’un click sur le bouton « archiver » d’un projet, seul un administrateur peut désarchiver un projet. Dans le cadre d’iceScrum Cloud, il faut donc faire appel à nous pour désarchiver un projet.

Les informations du projet seront alors effectivement disponible en lecture.

En revanche, le projet n’apparaîtra plus dans aucune liste (à part pour l’administrateur du serveur) il faudra donc y accéder par son URL.

Bonne fin de semaine

[Nicolas Noullet]

Bonjour Erik,

L’API est disponible depuis la dernière version (7.0.6) mais la documentation n’est pas encore disponible. Je vous ai écrit un email avec quelques détails concernant son utilisation en attendant que ces informations soient publiques.

[Nicolas Noullet]

You’re welcome.

Well I am afraid you come across other problems later in the process, but if you really want to give it a try:

The config.groovy file is not created automatically when starting iceScrum. It is rather created at the end of the setup wizard that is displayed at the first startup. If you never reached that point, that explains why you can’t find this file.

If you want to create it manually, you need to create a .icescrum directory and then config.groovy into it. The application will look for this .icescrum directory in the home of the user who starts it. If you have any doubt regarding what this home is, it should already contain a directory named icescrum.

In iceScrum R6, you need to tell iceScrum the URL that it will expose. This is done by setting the grails.serverURL entry in config.groovy. You will find an example in the config.groovy documentation.

[Nicolas Noullet]

Hi,

iceScrum 6 supports Java 6 and 7 while iceScrum 7 supports Java 7 and 8. This explains why you had more success with iceScrum 6.

Regardless of the iceScrum version, Websphere is not officially supported.

We rather recommend to install a standalone Tomcat where you can install the iceScrum war, or the use of icescrum.jar which contains its own Tomcat so you don’t have to install and maintain it.

In both cases, we strongly recommend the use of iceScrum 7 (hence Java 7 or 8). Indeed, iceScrum 6 will be deprecated very soon and Version 7 is a huge improvement over 6 as far as features or UI are concerned.

[Nicolas Noullet]

C’est corrigé dans la 7.0.6 qui n’est effectivement pas encore sortie, mais qui devrait sortir bientôt.

[Nicolas Noullet]

Désolé je reviens de congés et visiblement je n’ai pas encore raccroché tous les wagons, je reviens vers vous dès que j’ai du neuf.

[Nicolas Noullet]

Bonjour Christophe,

Quelle version de la v7 utilisez-vous ? Nous avons corrigé des problèmes dans l’interface des tests d’acceptation, nous recommandons d’utiliser la dernière version (7.0.6) disponible en téléchargement :
– jar : https://www.icescrum.com/download/v7-0/
– war : https://www.icescrum.com/download/v7-0-war/
– mise à jour : https://www.icescrum.com/documentation/upgrade-guide/

Nous n’avons pas reproduit votre problème sur la dernière version, j’attends vos retours pour savoir si ils persistent malgré tout de votre côté.

Nicolas

[Nicolas Noullet]

Once the current work on migrating all ressources to v7, we will ensure that all the tips and tricks get known!

[Nicolas Noullet]

Thanks for the additional information.

Do you use the same URL in the browser to open iceScrum from the PC than on the Mac?

Can you try with another browser on the mac? Do you have anything specific regarding network on the Mac? (VPN, proxy, firewall…)

[Nicolas Noullet]

Hi,

Could you provide additional information?
– The output of java -version
– The command you typed to start iceScrum
– Any error coming from the output of the startup command
– Any error in the /logs/icescrum.log file

That’s the first time we got this error and iceScrum appears to work fine on Mac OS, there must be something specific to your installation.

[Nicolas Noullet]

Hi, I sent you an email to help you but I didn’t get any response…

[Auteur]

Messages