iceScrum Forums Discuss on iceScrum
Forum Replies Created
Stories cannot be assigned to developers, and they should represent units of value provided to user, so they do not necessarily reflect the software architecture: one story can require both backend and frontend activities. Such stories are the responsibility of the whole team.
On the other hand, one task represent one activity, so it can be assigned to one developer (usually self-assigned rather than assigned by someone else, in order to follow the principle of self-managed team promoted by Scrum).
J’ai demandé la quantité de stories parce que si c’est normal que la requête prenne un temps proportionnel au nombre de stories, le temps que vous évoquez n’est pas du tout représentatif de ce que l’on constate normalement, on est plutôt à moins d’une seconde pour 100 stories sur un serveur configuré de manière nominale.
Il doit y avoir un problème relatif à votre serveur. Je vais vous contacter par email très prochainement pour la suite du support, cela sera plus adapté.
Pour ce qui est de l’optimisation de la requête, la plupart des données qui prennent du temps à charger sont celles qui sont justement sur le post-it…
Mais pour envisager des pistes adaptées à votre contexte, combien de stories avez-vous dans les backlogs qui prennent plus de 10 secondes à charger ?11/01/2021 at 2:20 pm in reply to: java.lang.IllegalStateException: BeanFactory not initialized or already closed #830922
Sure feel free to share it on the forum, this would be a great contribution to help the community! Thank you 🙂
Unfortunately turning that into an official guide is not a piece of cake: if we do ubuntu we should do redhat, windows server, for every DBMS, ensure that everything stays up to date, translate it in 3 different languages etc. That is why we do not provide precise guidance on how to configure external tools and we rather rely on the fact that they provide their own official documentations.07/01/2021 at 5:28 pm in reply to: java.lang.IllegalStateException: BeanFactory not initialized or already closed #829951
Different logs but same error, and same origin!
You can find the tables because part of it is supported, but it is bound to fail eventually. Downgrading to Postgres 11 should do the trick.07/01/2021 at 11:31 am in reply to: java.lang.IllegalStateException: BeanFactory not initialized or already closed #829737
I have edited your logs in order to reduce noise and avoid disclosing unnecessary information about your setup.
As you can see in what remains, you had two different errors.
The first one seemed to be related to a network issue between iceScrum and your PostgreSQL server. It seems that you managed to solve it as in the next restart we can see that iceScrum managed to reach it.
The second error happens when iceScrum sets up the databases on PostgreSQL. You get this error because you likely use a PostgreSQL version that is not supported by iceScrum, e.g. PostgreSQL 12.
iceScrum supports PostgreSQL version from 9.x to 11.x, see our documentation.05/01/2021 at 5:07 pm in reply to: java.lang.IllegalStateException: BeanFactory not initialized or already closed #829411
I am afraid that this error message does not tell much about what the error actually is. There should be another error before this one. Can you enable verbose logging and restart iceScrum again?
You can enable verbose logging by setting the following in the config.groovy file:
icescrum.debug.enable = true
Merci pour la suggestion, c’est ajouté dans notre Backlog 🙂
Sorry I thought I had answered, probably never clicked on “Submit”…
Value and Rank are différent things. As I said in the other thread, the Rank is the position of the item in the regular Backlog sorting order, which means that the story at the very top left is Ranked “1”, then the next is “2” etc. You can think of it as Music Charts, number 1 is the best !30/09/2020 at 9:07 am in reply to: What is “Rank” and how can I re-order my backlog items #804128
You are welcome 🙂29/09/2020 at 9:09 am in reply to: What is “Rank” and how can I re-order my backlog items #803759
You are correct, “Rank” means the position of the story in the default sorting order. This order represents the priorities according to the Product Owner.
Actually, the rank is implemented as a property of individual stories that you can find in exports, API etc. However, what really matters in the user interface is the resulting list. The rank of an individual story has little value on their own. That is why it is not displayed in the story details panel.
Changing the rank on an individual story without the context of the whole list would also have little value, as a Product Owner usually needs to position it relative to other stories. That is why the only way you can change it from a story details is to use the “Move to top priority” menu, which does not require additional context. Otherwise, you can change it by reordering stories by drag and drop in the list itself (only the Product Owner can do that).
It is offered as an explicit sorting criteria so that the default sorting criteria is shown and so that you can go back to it if you changed it temporarily. It is not called “Position” because when the sorting order is different, e.g. “Business Value”, then the actual visual position of the story changes and it not equal to its “Rank” anymore.
Does it make sense?
Thanks for your feedback.
For the moment the clues do not point in the same direction, so it’s hard to guess.
What we learned: it seems to be related to your computer, but probably not your iceScrum account, cookies or browsers or IP address. That is strange, so this should be confirmed if it happens again. Also, it disappears when restarting iceScrum.
Anyway I am glad that it works again! Feel free to come back if it happens again.
Thanks for your detailed report.
A way to trouble shoot this would consist in trying to isolate the problem.
If several browsers are affected then this looks like a network issue. You may first check the browser console and see what is the status of the HTTP response you get. There may be an explanation in the HTTP headers as well.
You may also use the command line to access iceScrum e.g.
If it still doesn’t work, then you may then try from another network connection, e.g. ethernet if you were using the Wi-Fi (and vice-versa). This will change your IP address as well as the network devices between you and iceScrum so the outcome may change.
You may also switch from ethernet to another ethernet cable or from Wi-FI to another Wi-Fi hotspot but there are less chances of success.
If your iceScrum server is accessible from the Internet then switching to another Internet connexion would also be very interesting.
Then expand the resulting list, and take a screenshot of the full console?
This will tell us what kind of validation error there is.
By the way if you just want to try iceScrum then you can register online and try it for free on our hosted Cloud platform.
There is no way to retroactively change the name of all instances of an actor in existing stories.
While it may seem like an obvious bug at first, it is actually a bit more subtle than that.
Indeed, the actor name is part of the story statement, which is often critical and carefully crafted by a human. Having a hard link so that the actor name change is automatically reflected everywhere is too radical. Indeed, when renaming an actor, you may just want upcoming stories to be affected by the change and not the one belonging to past sprints. Changing past stories indiscriminately could break the trust you have than when you write something, it stays as you wrote it unless you actively want to change it. That is why we decided to loosely couple the actor name so the hard link is made only on the ID.
In this case, automatic renaming should be provided as an option. However, a consequence of the loose link is that it that such automation is harder to implement, so with an agile mindset we decided to start without it and see if the need would arise. Until now we received very little feedback as the need to rename actors seldom occur and when it occurs, it is mainly at the very beginning of a project where changing the name manually on each story is quite inexpensive.
Anyway, your feedback is valuable for us and if we notice more interest for automatic renaming then we may implement it.