i would add to the conversation that the new backlog needs: 1. the ability to edit before a sprint starts 2. a summary of story points for each sprint 3. a summary of hours for each sprint 4.CSV download from the sprint view.
these are all features that are found in the old backlog and we miss them :( You may well have already planned to put them in the next release. -Craig On May 10, 9:23 am, Robert Buchholz <[email protected]> wrote: > On Monday 10 May 2010, akabat wrote: > > > It's more the new Sprint Backlog view that we don't like so much. > > That's too bad. It has become a lot more interactive, we've tried to > make editing easier and not harder. > > > 1. I cannot set the Status. I can edit the remaining time or the > > owner, but not the Status. > > You can reconfigure the backlog to display Status as a column. In the > next release, you'll be able to use the in place JavaScript editor for > all configured columns, so editing status works as well. > > > 2. In the old view the tickets were colored depending on the status > > which made it well-arranged. > > Yeah, we haven't figured out a way yet to mark assigned / closed > tickets. The next release will have buttons again to hide closed tickets > or tickets owned by someone else. Does that solve your issue? > > > Now, all the tickets are in the same > > color (black). By the way, can I configure the font colors or even > > the background colors? Configuring the background colors would be > > great! > > You can change colors by editing the CSS files. Have a look at > newbacklog.css for that. > > > 3. The font size is smaller or is it only an optical > > illusion? > > No illusion. It has changed from 12px to 11px. Again, newbacklog.css is > the place to edit theme internals. > > > So there's no possibility to open by default the old view? Maybe by > > renaming some files in the installation? > > No, there's no easy way I can think of. I'd much rather work with you to > make the new backlog great so you don't need the old backlog anymore > because you miss nothing about it. > > Regards > > Robert > > -- > -- > Follow Agilo on Twitter:http://twitter.com/agiloforscrum > Please support us by reviewing and voting > on:http://userstories.com/products/8-agilo-for-scrumhttp://ohloh.net/p/agilo-scrumhttp://freshmeat.net/projects/agiloforscrum > > You received this message because you are subscribed to the Google > Groups "Agilo for Scrum" group. This group is moderated by agile42 > GmbHhttp://www.agile42.comand is focused in supporting Agilo for Scrum > users.To post to this group, send email [email protected] > To unsubscribe from this group, send email > [email protected] > For more options, visit this group > athttp://groups.google.com/group/agilo?hl=en -- -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en
