[Nicolas Noullet]

Hello,

I am not sure that I understand your context, how could you use iceScrum if you did not restart it?

Anyway, to restart iceScrum you just have to kill the command (e.g. kill -1 on unix based environments, or CTRL+C) and start it again.

If you come across errors then you should provide your log files so we can investigate.

[Nicolas Noullet]

Hello Zoran,

Sorry for the delay and thanks for your feedback. For the moment our efforts are focused on iceScrum R7, which beta version should be ready soon, so we don’t consider planning new features for the moment. However, we take your feedback into account and iceScrum R7 will bring more customization options.

In the meantime, I can think about workarounds:

• Freeing either the notes or the tags, which may be not desirable because it changes the current conventions. This would also imply finding a way to express the content that was previously there (maybe the “Development” part could be moved to tasks (this is a blind guess, of course it really depends on your context)
• Mixing content in one of the fields
• Using the comments

Would one of these workarounds help?

Best regards

Nicolas

[Nicolas Noullet]

Bonjour,

Ce doublon est très probablement en cause et vu le contenu du champ version, le sprint 516 serait un sprint “fantôme” créé juste après le 515, et il n’est probablement pas utilisé dans l’application.

Le correctif consisterait à arrêter iceScrum, faire un backup de la base, supprimer la ligne d’icescrum2_timebox d’ID 516 et la ligne icescrum2_sprint d’ID 516 également, puis redémarrer iceScrum.

Il reste à déterminer comment un tel sprint a pu apparaître. Quelle version d’iceScrum utilisez-vous ?

[Nicolas Noullet]

Hello Zoran,

Unfortunately there is no way to add a custom field in the current version of iceScrum.

In order to understand your needs and consider improvements, can you tell me what would this field be?

Thanks,

Nicolas

[Nicolas Noullet]

Hello,

This would require some coding and it is not straightforward to do because background colors for post-its are part of a sprite (an image contains all the predefined background, css rules give the offset for each color).

The source code for iceScrum R6 is located here: https://github.com/icescrum/iceScrum-core/tree/R6%2313 and here: https://github.com/icescrum/iceScrum/tree/R6%2313

Making the change yourself may require more work that it is worth, but the code is here so it is up to you. Please note that in the R7 version which is currently under development (the master branch of these repositories), colors can be chosen in a color-picker and are displayed dynamically (no more predefined image).

[Nicolas Noullet]

Hello

There is not separate distinct .war, just download the existing .war and you get iceScrum community. You can add an iceScrum Pro license whenever you want to activate its feature (you can claim a 14 days free trial).

[Nicolas Noullet]

Hello,

Do you use iceScrum Cloud or iceScrum Standalone (on your server)

I am not sure that I understand your issue, maybe this can help you:

There is no way to register user through team/project management but if the option is enabled on the server, you can invite them by email.

Otherwise, users needs to register themselves or to be created by the iceScrum administrator (feature only available in iceScrum Pro) beforehand, and then you can add them in your team / project.

Regarding roles, a user cannot be team member in a team and product owner on the project which is associated to the team. The only project / team role combination that is allowed is Product Owner (project) / ScrumMaster (team).

[Nicolas Noullet]

Merci 😀

[Nicolas Noullet]

Bonjour,

Toujours pas de date désolé mais on s’en rapproche, tous nos efforts sont concentrés dessus !

[Nicolas Noullet]

Thanks,

Can you inspect the HTTP responses in your browser thanks to built-in developer tools:
– What is the status of the HTTP response for the checkplayer.js resource?
– What is the value of the Location header of this HTTP response?

If the only issue comes from the checkplayer resource then you can disable its loading by disabling the iceScrum chat feature. To do so, add the following to your config.groovy file and restart iceScrum:
icescrum.chat.enabled=false

[Nicolas Noullet]

Hi,

Can you provide:
– The command you use to start iceScrum
– The URL you want to use to open iceScrum
– The URL you are redirected to

[Nicolas Noullet]

Vous pouvez tenter d’arrêter iceScrum Server, vérifier que tous les process java / tomcat liés à iceScrum sont bien tués, supprimer tous les fichiers de logs, démarrer iceScrum Server, démarrer iceScrum et nous envoyer tous les fichiers de logs (server.log, icescrum.log, catalina…) ainsi qu’une capture d’écran d’iceScrum Server.

Même si aucune erreur ne se manifeste, ces informations pourront nous aider à comprendre le problème.

[Nicolas Noullet]

Thanks,

You need to customize the startup command in order configure the host, port etc., as indicated in the documentation : https://www.icescrum.com/documentation/install-guide/#start.

iceScrum can be accessed from only one URL and in your case I guess that you want to use the public IP one.

[Nicolas Noullet]

If you don’t use iceScrum Pro then you will have to export each project individually. To do so, you need to login with either the ScrumMaster or Product Owner permissions and open the project menu > Export.

If the menu is not visible then it indicates that exports are disabled in your configuration (config.groovy). The corresponding configuration entry is:
icescrum.project.export.enable

It is true by default but you may have changed it. Either remove this from your config:
icescrum.project.export.enable=false

Or change it to:
icescrum.project.export.enable=true

[Nicolas Noullet]

Quand ouvrez l’URL qui est indiquée dans l’interface d’iceScrum Serveur, qu’obtenez-vous dans votre navigateur ?

Est-ce qu’iceScrum fonctionne ?

Par défaut la clé de license est enregistrée dans le repertoire .icescrum de la home de l’utilisateur qui lance iceScrum. Si une clé est prise en compte vous pouvez également la supprimer directement depuis l’interface d’iceScrum (si iceScrum arrive à se lancer) en étant connecté avec le compte administrateur, après avoir cliqué sur le logo IS en haut à gauche. Ceci dit, une clé qui n’est plus valide ne devrait pas poser de problème, iceScrum bascule automatiquement en version community.

[Author]

Posts