Your comments

Hi Julie

Thanks for the feedback.

We are in fact planning this feature, however it's not been high on our priority lists to date because we've been quite purist in our approach encouraging people to use physical boards for this type of assignment.  easyBacklog was not designed to replace physical scrum boards, and certainly not meant to be a collaboration tool.  However, we have got a lot of valuable feedback from our customers whereby they are telling us that there are valid reasons why people need scrum boards, need assignment of stories and or tasks to users.

Unfortunately this feature is a good few weeks away at least, but as soon the feature is ready I'll be sure to drop you a line so that you can try it out.

May I ask, the one thing you did mention is that a story can be assigned to one or more people.  Is that common or quite rare for you to have multiple people assigned?  Also, if we did not allow a story to be assigned to a user, but instead only allowed one more story tasks to be assigned to a single user, do you think that would work?  Basically, we believe that once you move a story into a sprint, you will typically break each task down.  Then as each task is owned / taken on by a user, he/she will assign it to themselves.  We are not sure that more than one person should ever own a single task.  And we are not really sure a story should be owned by a user, but instead the tasks should be owned by a user.

What are your thoughts on that?
Hi Sherry

Sorry to hear that it's not working for you.  I just emulated your user from our admin section, and tried the demo, and it seemed to work.

Can you tell me what what browser you are using?  Also, can you tell me what exactly happens when it stops working / how far you get?

Thanks,
Matt
Hi Michael

I thought it was obvious which stories are assigned to a sprint based on the lozenges that are attached to each story.  See the screen shot below that shows stories that are assigned to sprints.

Is that not what you are after?
Matt
Hi there

We are a bit reluctant to add more fields to the interface as it's already pretty crowded as it is.  However, saying that, a few people have been asking about a separate priority field, which perhaps could have a dual purpose of release / priority, which you could then sort by.  Can you explain a little more about how you use this release field so I can understand the process?

Matt
Hi Michael

Sorry to hear that, not head that of that problem with others so perhaps a browser compatibility issue.  What browser are you using?  I realise the problem may be erratic, but is there any way you could suggest I could somehow replicate this issue?

Thanks,
Matt
Hi Michael

Would you mind sending me a screen shot, and possibly some basic instructions on how to replicate the issue?  Also, what browser are you using?

Matt
Ah, that's an interesting point.  I suppose the problem is that if we don't provide all those summary fields, then you won't get all the nice summary and ancillary information that is presented in the report.  Mind telling me how you use the report, and what you're trying to do so I can get a better understand of the business need?
Hi Michael

Colours in the sprint view are now retained for stories.

Matt
Fortunately this is our top priority now too.

We should have a solution very shortly.

Matt