[Nicolas Noullet]

Thanks for the report, this seems to be a bug. We are working on it.

[Nicolas Noullet]

The R6#14.1 version does not require MySQL: just as the R6#3 it can work with HSQLDB.

However, as explained in our documentation, the use of HSQLDB is not recommend for real life usages because it is not reliable.

The procedure to migrate from a DBMS to another consists in exporting your projects from iceScrum itself and importing them when you have switched to the new DBMS.

[Nicolas Noullet]

Hi Xavier,

Thanks for the update. There must be another error in the logs. You can enable more verbose logging by changing this line in config.groovy:
icescrum.debug.enable = true

Then, you can check the content of icescrum.log and catalina.out and look for an error (the TEXT_AS error excluded, you can check the common errors in the documentation: https://www.icescrum.com/documentation/install-guide/#troubleshooting_2)

[Nicolas Noullet]

This is why I asked you about your version.

Indeed, iceScrum R6#14 gives more importance to the team than before and the project creator / owner is now computer from the team owner.

Than means that a team owner has full permissions on all the projects associated with the team, and you cannot change the project creator individually.

[Nicolas Noullet]

You need to be connected as the administrator in order to do so.

What version of icesScrum do you use?

[Nicolas Noullet]

There is currently no plan to do so.

[Nicolas Noullet]

Hi Vivek,

When you click on a team in the dropdown, your browser executes javascript code that should enable the “next” button.

Can you try again with the Chrome development console opened and provide its content? (https://developer.chrome.com/devtools). If there is any error then it should be displayed there.

[Nicolas Noullet]

Hi Caroline,

Sorry for the late answer. Actually I have written an anwer before but it seemed that I never submitted it.

This is a nasty long standing bug that affects projects which timezone is before UTC (which I assume is your case?). Sprint dates are mistakenly converted to the project timezone when they are displayed in the Sprint plan / Release plan, that is why they are shown one day before the date actually stored in iceScrum (the date shown in the Update / REST API).

This issue should definitely be solved! However, many teams rely on the displayed dates, which are wrong, and fixing them will probably cause some trouble.

[Nicolas Noullet]

Hello Clarence,

You have to click on a link below named “All downloads for iceScrum …” in order to display all the downloads, including the one you are looking for that is named “iceScrum Server”. It is not easy to find, we will make that clearer.

Please note that this installer is suited for demo or evaluation but not for production environments, and that it requires a proper Java 6 or 7 installation. You will find more information about iceScrum Server here: https://www.icescrum.com/documentation/using-icescrum-server/

[Nicolas Noullet]

Glad to know that 🙂

[Nicolas Noullet]

Bonjour,

Rien de particulier pour Windows ou Linux.

En revanche, comme indiqué dans le tableau de comparaison des versions (https://www.icescrum.com/pricing/#comparison) Oracle n’est supporté que dans iceScrum Pro Standalone (que vous pouvez essayer gratuitement pour 14 jours).

Voici la documentation correspondante : https://www.icescrum.com/documentation/administration/#administration-settings_5

[Nicolas Noullet]

Hello,

Out of memory errors usually come from JVM misconfigurations regarding memory.

Here, you have defined a correct Heap Space (-Xmx512m) but you forgot the PermGen space:
-XX:MaxPermSize=256m

See https://www.icescrum.com/documentation/install-guide/#application-server

[Nicolas Noullet]

Hello,

User management is an iceScrum Pro Standalone feature, you will find more information in the dedicated documentation: https://www.icescrum.com/documentation/administration/#administration-users

On iceScrum Community, users register themselves and they cannot be updated by another user.

[Nicolas Noullet]

According to the Mantis issue I linked, the bug is fixed in Mantis 1.2.14 (1.2.13 should not be used).

However, as indicated in our documentation (https://www.icescrum.com/documentation/icescrum-pro/bug-tracker/), we support the integration only for Mantis 1.2.15 and greater.

Please let us know if you come across any other issue when once this one is addressed.

[Nicolas Noullet]

Hi,

Which version of Mantis do you use?

The error message indicates that the problem probably comes from your Mantis installation, see https://www.mantisbt.org/bugs/view.php?id=14157

[Author]

Posts