On 08/04, Lukas Zapletal wrote: > Please, can we please not create these crazy "backlogs" and the dance > around and just use RedMine as it was design for? Otherwise we will be > doing nothing but tossing tickets from backlog to backlog.
The idea is to do that in 30m or so every two weeks > * Put an item on "backlog" = create new Feature, NEW state > > * Put it on "sprint" = associate with feature issue (*) > > * Resolve issue, set Target Foreman version we ship it into > > * Profit! This is what we've been doing for some time, the process is fine but how can you prioritize a backlog of 6488 open issues? If the answer is adding the ones we think are most important to an etherpad, it's Pruning the search results to only show 'categories' owned by a team or certain plugins, isn't a good solution for getting less issues, as that field isn't that reliable & still returns 1000s of issues I'm all open to ideas that allow us to have a concise backlog we can prioritize from -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
