[Nicolas Noullet]

Thanks for your enthusiasm! 🙂

The current iceScrum version is the result of years of iterations based on what was the best at the times in terms of UI/UX for webapps. However, things have changed a lot in this domain and we think that iceScrum could be easier to use, the user experience improved and the UI more pleasant to the eyes. Thus, we are currently developing a brand new UI/UX (and some nice new features) under the name iceScrum R7. You can read more about it here: https://www.icescrum.com/blog/a-bright-future-for-icescrum/

[Nicolas Noullet]

I am glad that you solved the issue!

To test it, there is a « test » button in the iceScrum Pro administration, see https://www.icescrum.com/documentation/administration/#administration-settings_3. This requires an active license and if you don’t have one you can get a free 14 days trial license on our website, this only requires you to be registered. After the license is expired, you can keep using iceScrum just as before.

Keep in mind that you will need two users because the user who triggers the action is excluded from the recipients, here is how most emails are sent:

• New story / task: in their profile, a user can choose to receive an email for any new story (or task in current sprint) created by someone else.
• Follow story updates: a user who follows a story receives an email for any update / comment made by someone else on this story.

There are several ways to follow a story:

• Create/comment a story, you become follower automatically
• Click on « follow » in the story details
• Enable « follow new stories » in your profile. This is not retroactive, only stories created after that will trigger an email when they will be update later on

[Nicolas Noullet]

Hi,

Where did you get the « template » for this configuration? It seems to be correct but our forum converts regular double quotes to stylized ones which will not work in config.groovy. Therefore, if you copied this configuration from our forum then you need to replace all the double quotes which regular ones.

If the quotes are fine then this can be either:

• Alerts are not enabled (you can check that icescrum.alerts.enable = true)
• A network issue prevents your server to communicate with the gmail SMTP server on port 465
• Your config.groovy is not taken into account. You can try to change another configuration entry, restart your server and check if it is taken into account.

[Nicolas Noullet]

Hello Adrian

Thanks for your detailed feedback (if all issue reports were like this, my life would be easier!).

I agree that this animation is misleading, but we have no plan to fix it. Indeed, the iceScrum UI is now a bit dated and while the technology we used at the time was the very best available, there are now much better tools to build good UI/UX. Thus, we currently focus our efforts on the development of a brand new UI for iceScrum, alongside with other improvements. It will be released under the name « iceScrum R7 ».

I can give you access to a private Alpha version of iceScrum R7 if you want to try it and provide your feedback on the new interface.

In the meantime, I would recommend that you ignore the animation and only take into account the final state: if the story is not in the Sandbox and has moved to the backlog then it worked.

[Nicolas Noullet]

Marcus,

I sent you an email but you did not answer, is your problem solved?

Nicolas

[Nicolas Noullet]

You’re welcome,

I confirm that the master branch is iceScrum R7, it makes use of the latest Bootstrap / Angular 1 libraries on the client side and should keep up with the 2.5.X grails version in the backend (grails 3.X.X breaks many things and is more micro-service oriented so for the moment we don’t plan to upgrade).

I am curious: by predicting sprint progress you mean the progress of tasks inside a sprint, or progress of done stories sprint by sprint?

[Nicolas Noullet]

Hello,

The current released version, iceScrum R6, is quite difficult to setup and will be deprecated by iceScrum R7 in the upcoming months. The whole front-end and large parts of the backend have changed (in a good way) in iceScrum R7 so I would not recommend investing in iceScrum R6.

We currently focus on iceScrum R7 development and we don’t have the resources to facilitate and support community developments yet, and some parts are still subject to changes.

Anyway, thanks for your interest! Can you tell us about the additional features you would like to implement?

[Nicolas Noullet]

Did you rename the .war file to ROOT.war ?

[Nicolas Noullet]

Hello Marcus,

We « iceScrum standalone » stands for both the .jar and the .war versions, « standalone » just means that you install iceScrum on your own server rather than on our Cloud.

I confirm that the .jar version cannot be used in combination with a reverse Proxy, whereas the .war version with a custom Tomcat can!

You are heading in the right direction, but there are two remaining problems:

• The context name (here the /icescrum that comes at the end of the iceScrum URL) must be the same for the public URL and internal URL (it’s a limitation of a library we use).
  That means that you can either have
  – http://tomcat_ip:8080/icescrum/ and https://icescrum.mydomain.com/icescrum
  – or http://tomcat_ip:8080/ and https://icescrum.mydomain.com, which seems to be better. To make iceScrum start on the empty context on Tomcat, rename icescrum.war to ROOT.war and restart Tomcat
• You didn’t change the connector to be NIO and iceScrum will not work properly with BIO, change it in your server.xml as explained in the documentation: https://www.icescrum.com/documentation/application-server/

[Nicolas Noullet]

Pas de date pour la version définitive car elle dépendra de ce que donne la beta, qui quant à elle sortira courant mars !

[Nicolas Noullet]

You can first query all the releases, as offered by the first request here: https://www.icescrum.com/documentation/release-api/
You will get all the releases details, which include their ID.

Then you can use the request « Get all sprints for a given release » provided here with the ID of the release of your choice: https://www.icescrum.com/documentation/sprint-api/

[Nicolas Noullet]

Bonjour Christophe,

Ce n’est pas possible pour le moment, et ce sera effectivement possible dans la version R7 (plus d’infos sur cette version : https://www.icescrum.com/blog/a-bright-future-for-icescrum/

Nicolas

[Nicolas Noullet]

Hi,

Yes I did receive them and I did not forget you but I had to finish my ongoing work. I will look at your exports today.

[Nicolas Noullet]

No problem 🙂

[Nicolas Noullet]

Hi,

Can you send me the failing export files? nnoullet _ at _ kagilum _ dot _ com

[Auteur]

Messages