In response to your last comment about stats per release, that is something we would consider.  However, we did not really consider how releases would work for live sprints, only as an after thought to group sprints into releases.  When we introduce this functionality, I'll certainly consider this.  Unfortunately release management is a bit of a way down our backlog so that won't be introduced very soon.

Matt

We have now improved the usability of this based on your suggestion.  It was in fact a little more complex than a text change as Cancel is appropriate once changes are made, however Back is more appropriate if no changes have been made yet, so the button text changes automatically as appropriate.

Thanks for the feedback.

Matt

On your first point about the open/collapse not remembering the stories that are filtered, we have fixed that bug now.  Our first stab at writing the filtering engine for the view was a bit rudimentary, so we've completely rewritten it now and I believe is way more robust.  Shout if you run into any problems.

In terms of a default filter, we are now planning on including a system to remember your last filter settings along with which themes you have collapsed or not.  I will update this post when that feature is released.

Matt

Thanks for the good idea.  We've taken on board your suggestion and modified the export feature of easyBacklog now so that it does the following:

• Uses Microsoft Xml Xls format for the spreadsheet allowing more complex spreadsheets to be built so that we could support this feature
• We now create two Worksheet Tabs when you export your Backlog, the first one "Backlog Report" is very similar to what you saw before.  However, the second one "Story List" is a complete list of stories without spaces, and an Auto-filter applied  to the top header row so you can filter the stories as you wish.

Thanks again for the feedback.

Matt

Thanks for the feedback.

In order to see if we can help you, can you explain at what point you split stories.  And when you split stories, what happens to the story you have split, is it disregarded?  I have spoken with a few users who have this need, and they say the normally add a new story and simply reduce the scope of the existing epic.  Does this not work for you?  If not, please explain your process and let me see what we can do.

Matt

I've just tried to replicate this problem again and just can't do it.  I'd really appreciate it if you wouldn't mind taking the time to explain how I can replicate this problem.

Thanks,
Matt

Sorry for the inconvenience.

We've had this reported before, see http://easybacklog.userecho.com/topic/93299-sometimes-new-story-button-disappears/, but have never been able to replicate this issue.

I know this is tedious for you, but as we've never been able to replicate the issue, is there any way you can tell us how to replicate the problem so we can fix it?  Also, are you on PC/Mac?

Matt

In regards to point 1, I'm not really clear on what the issue is.  If story 2 is part of a later release, why is that a problem if it's part of the user login/logout theme?

In regards to point 2, I feel your pain.  Big lengthy backlogs are very hard to maintain, and I'm not sure we have a solution at present for this.  The problem with numbering systems is that if you want to introduce a bunch of stories above others, then potentially you have to spend loads of time renumbering old items to shift everything around.  Hence we are considering a drag and drop solution instead that is divorced from theme ordering, but will allow you to maintain your backlog ordering easily.  Do you not think this would work for you?  If not, why?

Matt

Sorry for taking so long to reply.  You are correct, this is a bug.  We will prioritise a fix for this very soon, we're just writing the tests to replicate this problem and then we'll get the fix implemented.  Sorry for the inconvenience.

Matt