[Nicolas Noullet]

Hi, you should have received an email

[Nicolas Noullet]

Hi,

Can you tell us precisely which version of Java 7 and Tomcat 7 you use?

There is no built-in attachment on the forum. You can upload them on an online storing service (dropbox, google drive, https://gist.github.com/…) or send them by email at: nnoullet at kagilum . com.

[Nicolas Noullet]

I hope that you like it and I am looking forward to hearing your feedback 🙂

[Nicolas Noullet]

You are right, the version is important. We use Grails 2.x, the latest being Grails is 2.5.4. It should build fine and you can get a .war file by using the grails war command. You can then run this .war in a Tomcat server as explained here: https://www.icescrum.com/documentation/application-server/#application-server_1

Unfortunately setting up a full development environment is way more complicated than that. As I told you, we will work on that as soon as we have the time to do so, which means after the release of iceScrum 7. The preferred way to contribute to iceScrum will be via Grails plugins. We will provide a plugin template and explain how to hook into existing iceScrum features. The plumbing for that already works but it will probably change until we have ported all the iceScrum Pro features.

By having an account on our website, you should be able to use the beta! Just follow the link in the banner or open this link http://beta.icescrum.com

[Nicolas Noullet]

Hello Fred,

That’s really strange! iceScrum either comes without Tomcat (it’s a simple .war file that you have to deploy in your own Tomcat) or as a .jar file that contains its own Tomcat 7.0.52.

For how long have you been using iceScrum? Even the “iceScrum Server” installer which has been deprecated a long time ago came with Tomcat 7.0.29…

[Nicolas Noullet]

Avec plaisir, content que le problème soit réglé ! 🙂

[Nicolas Noullet]

Bonjour,

Voici quelques questions pour essayer d’y voir plus clair :
– Est-ce que toutes les stories sont affectées ?
– Est-ce que les fichiers indiqués dans les logs d’erreur existent au chemin spécifié ?
— Si oui, est-ce que l’utilisateur qui lance iceScrum a bien les permissions en execution sur tous les dossiers parents et les droits en lecture sur le fichier ?
— Si non, est-ce que ces fichiers se trouvent ailleurs ? (par ex. un find sur le nom de fichier)

A priori nous ne voyons pas de changement entre R6#14.7 et R6#14.10 qui pourraient causer ce problème, il s’agit donc peut être d’un changement de votre configuration au moment de la mise à jour.

Nicolas

[Nicolas Noullet]

Thanks for your feedback.

You are right, we have been talking about iceScrum R7 for a long time. It took many more iterations than what we expected but we did not want to rush into when defining the ground for the future of the tool. Also, we stopped writing newsletters for a while and we rather focused on blog posts in addition to better content on the website. We are actually focusing all our efforts on iceScrum R7, here is a recent blog post about iceScrum R7: https://www.icescrum.com/blog/a-bright-future-for-icescrum/

For the moment our policy regarding source code is exactly the same as before, that means that all the iceScrum “community” source code is freely available on GitHub. Sources for iceScrum R7 is actually on the master branches of our repositories: https://github.com/icescrum/iceScrum.

Contributing to iceScrum R6 required a deep understanding of the custom architecture that we designed at a time where no good public alternative existed. We are building iceScrum R7 on top of modern and well defined technology and contributions in the form of extensions / plugins was in our mind from the beginning so contributions should be way easier.

A public beta version in expected to be available online within a week (at first we will not release standalone versions). However we will probably wait until it is production ready before providing tools (extension templates / documentation…) to facilitate contributions.

Recording the time spent to actually develop a task is a topic we discussed a lot and we will be glad to exchange with you about that when we will be less busy!

[Nicolas Noullet]

Hello Fred,

For a Tomcat 7 install iceScrum requires at least 7.0.23 (Tomcat 8 is not supported yet), as explained in our documentation: https://www.icescrum.com/documentation/application-server. Former versions had bugs that prevent nominal use of iceScrum and there are good chances that this is the cause of your issue.

Also, is your Tomcat connector configured to use the NIO protocol ? If not then it can also cause similar issues.

[Nicolas Noullet]

Hello,

Thanks a lot for your interest in contributing to iceScrum!

The current released version, iceScrum R6, is rather 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 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.

Can you tell us about the additional features you would like to implement?

[Nicolas Noullet]

Hello,

While SAFe is rather popular, there is no general consensus in the agile community regarding the proper way to “scale” agile methodologies. That’s why iceScrum does not implement SAFe and only provide lightweight ways to scale Scrum projects.

However, one can attach custom data to iceScrum items. You can maintain a list of Epics outside of iceScrum and add a tag to features according to their Epic.

[Nicolas Noullet]

Hello Caroline

Here is how notification 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 to become “follower” of 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

The only way to “unfollow” a story consists in clicking on “unfollow” in its details.

There is no more detailed way to manage notifications in iceScrum, mainly because we don’t and it to be a nightmare in configuration options. However, you should be able to easily filter the type of notification further by creating filters in your email client.

[Nicolas Noullet]

Don’t worry I did not forget you! 😉

[Nicolas Noullet]

Hi,

Thanks for taking the time to explain your point, I understand it better now and it think that it is a good idea, thanks for suggesting it!

Right now all our efforts are focused on publishing iceScrum R7 beta, which scope is frozen now, but we will keep this suggestion in mind.

[Nicolas Noullet]

Hello,

There is no way to track individual contributions to a sprint other than the task filter.

This is intentional. Indeed, such feature can be easily abused and favor micro-management whereas agile methodologies rather encourage shared responsibility (both for success and failures) and collective discussions regarding improvements (through “retrospective” meetings).

To be successful, this requires communication, mutual trust, honesty, transparency… which is not easy to get but we want agile teams to head towards these values rather than helping them keeping the opposite ones.

[Author]

Posts