[Kagilum]

I use MantisBT 1.2.11
There is a problem: I have no access to Mantis Installation. I’ll contact Mantis’ responsible. Thanks

[Kagilum]

Nicolas,
We tried your solution yesterday and it worked! Thank you so much!

[Kagilum]

Nicolas,
Thank you for updating my curl command.

As you mentioned, since the GUI will not let us update the startDate once the sprint has been activated, neither will the API.

Any suggestions for how to fix the original problem? Below is a reworded description:

We have a project that was setup and activated on 04/29/2015. The startDate somehow ended up being set to 05/30/2015 rather than the ideal 04/30/2015. Due to this problem, we cannot close the sprint because the endDate is before the startDate.

Can you point us to the database tables we would need to update? Otherwise we will not be able to close this sprint and start a new one until 06/15/2015.

[Kagilum]

First of all, a quick note on how useful I think IceScrum is. It has saved us from having to maintain a physical scrum board, and it generates burn down graphs. Neato!

That said, I can’t help but get the feeling from this discussion that there are other reasons why it’s not possible to add an extra status column (for instance, because it means a lot of work to make the existing functionality flexible w.r.t. the number and meaning of status columns).

“Forcing” how Scrum teams should work shouldn’t be a reason; teams should be able to decide themselves. We use a code review, and would like to indicate that a particular issue is “IN REVIEW”. A column would help.

As a workaround, we could for the moment use the comments or task description to add a link to the code review. Do you have a better suggestion?

Anyways, Thanks!

[Kagilum]

Bonjour,

Avez-vous bien reçu mon mail ce matin comprenant le projet?

Merci pour votre aide,
Cordialement,

[Kagilum]

Bonjour,

Je viens de vous envoyer un mail.

Merci,

[Kagilum]

Merci pour votre réponse.

Dans sa dernière édition de son livre sur la méthode Scrum, Claude Aubry ne préconise plus d’estimer les tâches en heures. Pensez-vous que cet indicateur (burndown de sprint en points) pourrait faire l’objet d’une nouvelle feature pour IceScrum ?

Je tenais aussi à féliciter toute l’équipe pour le travail accompli.

[Kagilum]

Merci.

[Kagilum]

Thank you very much, Nicolas!! It worked. Thanks for the quick support. Appreciate your help.

[Kagilum]

Thanks!

2015-04-08 07:04:49,243 [localhost-startStop-1] ERROR org.springframework.web.context.ContextLoader – Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘pluginManager’ defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is org.codehaus.groovy.grails.exceptions.NewInstanceCreationException: Could not create a new instance of class [AutobaseGrailsPlugin]!
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.codehaus.groovy.grails.exceptions.NewInstanceCreationException: Could not create a new instance of class [AutobaseGrailsPlugin]!
… 5 more
Caused by: java.lang.NoClassDefFoundError: autobase.migration.MigrationArtefactHandler
at AutobaseGrailsPlugin.class$(AutobaseGrailsPlugin.groovy)
at AutobaseGrailsPlugin.$get$$class$autobase$migration$MigrationArtefactHandler(AutobaseGrailsPlugin.groovy)
at AutobaseGrailsPlugin.(AutobaseGrailsPlugin.groovy:60)
… 5 more

[Kagilum]

Where can I find the icescrum.log file? This is from the catalina log file under tomcat>logs

INFO: Using a shared selector for servlet write/read
Apr 08, 2015 8:20:55 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [“ajp-bio-8009”]
Apr 08, 2015 8:20:55 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2753 ms
Apr 08, 2015 8:20:55 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Apr 08, 2015 8:20:55 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.29
Apr 08, 2015 8:20:55 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:Program Files (x86)KagilumiceScrum Servertomcatwebappsicescrum
Apr 08, 2015 8:20:58 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(C:Program Files (x86)KagilumiceScrum ServertomcatwebappsicescrumWEB-INFlibgeronimo-servlet_3.0_spec-1.0.jar) – jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Apr 08, 2015 8:23:08 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
Apr 08, 2015 8:23:08 AM org.apache.catalina.util.SessionIdGenerator createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [172] milliseconds.
Apr 08, 2015 8:23:08 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/icescrum] startup failed due to previous errors
Apr 08, 2015 8:23:08 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [“http-nio-8080”]
Apr 08, 2015 8:23:09 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [“ajp-bio-8009”]
Apr 08, 2015 8:23:09 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 133689 ms

[Kagilum]

Ok! I will be expecting 🙂

[Kagilum]

Bon, pour info, ça marche.

J’ai fait un mix de deux posts.

Installation de JAKARTA*
et

Stop TOMCAT
Suppression contenu de tomcat/work/ et de tomcat/webapps/icescrum/
Start TOMCAT

Cordialement.

[Kagilum]

If you click the “IS” icon in the top left of the web interface, it will display a lot of information about the versions of software in use.

[Kagilum]

Thank you! I’m currently circumventing this issue by just using JSON, but it seemed like it was a problem with data returned as XML attributes. Hopefully, this will fix the problem I’ve been having.

I was already setting both accept and content-type as “application/xml” in my code for all requests, but I had only been specifying one in my curl requests.
I also had issues with feature.id and sprint.id in creating stories and updating stories, which I have been circumventing by using the separate 2 requests for specifically associating a feature or planning in a sprint, but this probably resolves those issues as well.

[Author]

Posts