misleading error messages when adding/dropping story to locked sprint

[inger]

platform: 2.2.2 # supported: 2.0.4, 2.1.6, 2.2.3
backlogs: 0.9.35 a09d5a6 # supported: 0.9.36
ruby: 1.9.3 # supported: 1.9.3, 1.8.7

On the backlogs page, pick a sprint that has its version in a "locked" status.

Pressing "New story" there, yields popup error: "Validation failed: Target version is not included in the list"

Drag&dropping a story there yields untranslated error: "translation missing: en.field_fixed_version_id translation missing: en.error_is not included in the list"

[patrickatamaniuk]

Sidenote: locked versions cannot assign neither tasks nor stories - so they would be not useful in a running sprint where the team may add tasks to a story.

What is your intention of locking a version? Can you workaround by not using the locked state in current sprints?

[inger]

locked versions cannot assign neither tasks nor stories - so they would be not useful in a running sprint where the team may add tasks to a story

Sure I'd consider this an error condition, ideally with a message what the "story" is:)

What is your intention of locking a version?

It wasn't my intention, I just happened to have a db (I think some example setup with eCookbook project etc..).
As a smoke test I opened a taskboard for 2 sprints, both looking the same on the backlog page, and on taskboard too for the first glance. So I was surprised to see the different behaviour. I'd just give user a bit more hint : a better msg and/or some visual hint (tooltip, greyed out sprint or something like that)..

[patrickatamaniuk]

I'd just give user a bit more hint

Of course the condition should be handled gracefully. I just was not sure if there is a good reason to want/need locked versions in the context of backlogs.

Greyed out sprint would be a good solution.
Not showing locked versions at all would be even easier, but could confuse users. Im indecided right now.

[inger]

Not showing locked versions at all would be even easier

That would be then the same handling as for closed sprints/versions.. I'm not 100% sure on the intended usage differences of closed vs locked versions - but I agree, maybe from RBL point of view they could be handled the same way..

OTOH, another question is what the common handling should be. Now that I think of it, I remember that I did want to look at older sprints a few times, and really see them as a sprint, eg look at the burndown..perhaps useful for retrospectives too.

So from this point of view, I'd prefer a quick filter option to show closed/=locked sprints.. maybe "Show completed sprints" in View options? Maybe I should raise another story for this.

[patrickatamaniuk]

following http://www.redmine.org/boards/2/topics/18914 and http://www.redmine.org/projects/redmine/wiki/RedmineProjectSettings#Versions i simply disabled the 'create new issue' menus for locked versions. The actual error message you have seen is coming from deep within redmine, no real influence on usablilty there.