As a scrumpy user planning a release or sprint, I'd like to be able to sort the stories table for my product based on the release or sprint, so that all unassigned stories are grouped together, and so I can see the product progression based on releases and sprints.

Acceptance Criteria)
1. I can sort the story table for a product by release then by sprint by clicking on the "Release" column header
2. More generally, I'd like to sort based on any column by clicking the column header
3. (not required, but nice to have) Clicking a column a second time sorts in the other direction. Clicking a third time reverts back to the default sort.

Apologies for the delay in getting back to you. I have now moved house but still have an unresolved problem with my Internet access. Hopefully normal service will be resumed shortly :)

Hmm. I appreciate that when people see a table they automatically expect to be able to sort by any of the columns available.

Scrumpy however strictly maintains the priority order of the Stories on purpose. I did this to re-enforce the idea that a Scrum Product Backlog is a prioritised list of items and to force the Product Owner to decide what the priority is. Similarly there is no support for the “MoSCoW” method of prioritisation. If you have two “Must haves” which one does the Team do first?

In practice I generally find that the Product Backlog is ‘self-ordering’ with respect to Sprints and Releases. When we are doing it right the most important stuff gets scheduled into the next Sprint and shipped in the next Release. Unscheduled items usually stick out like a sore thumb when I click the “Hide Done” check-box at the bottom of the “Backlog” tab.

I think that “Acceptance Criteria #1” can be met currently by selecting that Release in the Portfolio Tree on the LHS. This will show you just the Stories for that Release.

Hope this makes some sense. Thanks again for taking the time to make the suggestion.