Hi Matt,

i showed your answer some of my buddies here and everybody is happy to get this feature, including me, Thanks!

Roger

Always glad to help making a cool software even cooler :)

Releases would be so cool, i really looking forward to get hands on this!
Feel free to ask me, if u want an quick answer or simply want to hear my opinion feel free to e-mail me.

Hi Matt,

remembering the last filter sounds best for me. This way you can handle multiple users with different interests and everybody can filter to achieve his goals.

By the way, if u start to remeber filter settings could you then remember the open/collapse state of the themes also?
Its getting annoying if u have many UserStorys and want to edit the last theme in backlog but you have to scroll and collapse all the time the same themes again and again.

I need to know which one of the sprints is the current one.
Also i dont want the backlog to get messed up with tons of allready completet sprints so i want to archivate sprints. They shouldnt be visible as tabs then but still present in the statistics.

Another way to show you what i want to achieve.

Create a new Backlog,
Now add 20 Sprints to the Backlog.

And then imagine this is the product you are working currently on and then tell me which sprint is currently under development.

And then imagine you know that there will be at least 20 more sprints or maybe more.
That Tabview is not flexible enough to handle many sprints and gets messed up.

Does this help you to understand my point of view?

Thanks Matthew,

now i found the button, thanks for planning an optimization there.

The Problem about this specific button is that easyBacklog is an WebApplication.
If u are on a Website u are expecting to jump to the start page when u click there so if u just want to go to the previous site u dont expect anything at this position.

Thanks, i will take a look at it when it goes live.
Sounds like it can solve many of the problems.

finally found that expand button...
its not really cool but ok it solves the problem once you find that button

no not really integration that would be way too much,
All i need is the possibility that this ticket number is shown in sprintview (and story cards).
Thats the real value of this story for me.

if i can configure a link where this ticketnumber will be added, that would be the super deluxe version but to enter the number and make it visible in sprint view would be enough.

Hi Matthew,

understood the problems i think of a much simpler solution now. Because there are not many products, its a single product with customizations for different customers the solution with different backlogs isnt very usefull. The single projects/customer specific things are just too small to handle it as a full product. I also had to plan single user storys from different customers into an sprint (sometimes bugfixing sometimes really small changes). Running Sprints for Customer A and then for Customer B is the goal i want to achieve but in the real world i always have TODOs from other customers, especially when there are really small changes.

Copying User Storys is also not a good idea, because thats a copy and if there are changes i had to do the changes on 2 places (human error cries out loud ;) )

But I have another idea which would solve my current problems and should be much simpler to implement. The possibility to add a Customer to a Theme. And i need to minimize the view per customer just like Themes.

Then i can group by customers and can create themes per customer.

A cool right management where i can choose who can edit which customer and who can edit sprints would be perfect at the end.

Does this make sense to you?

Oh and by the way, thanks for that great support and your help in that brainstorming and testing phase!

Hi Matthew,

i tried it but it doesnt work very well.
Problem is i had to give the other user full access to the central backlog because with read only access the in target backlog i can't move themes there. To make this work i need a bit more possibilities from an right management point of view.

Even then its not very cool that i just can move whole themes and not single user storys (because in central backlog the themes are customer names and in customer backlogs they have "real" themes).

Another thing i had to check is if i can move the userstory back to the customers backlog when im done because its still in an completed sprint. This isnt a must have requirement but helps the customer project manager to keep track of his customer.

Seems like easy backlog is quite cool for a single product but doesnt work very well if you have more products handeled by a single team currently.