intrigeri a écrit : > Hi, > > sajol...@pimienta.org wrote (15 Sep 2014 14:32:15 GMT) : >> intrigeri wrote: > >> Unless we decide to have only one axe in those categories, they are >> bound to overlaps sometimes. When I have to choose between two things, I >> choose the "tool" over the "field of expertise". > > I very well see what you mean, and I've seen BitingBird struggle with > this too when triaging tickets.
Yep, I do, because it's quite arbitrary really, which category wins when 2 are concerned :) > >> The real solution would be to allow multiple values for Categories. >> That's more like tag system with predefined value. Does this exist in >> Redmine? The notion of "Category" is pretty bad anyway for picky people >> like us... > > Nope, this is not possible in Redmine. However, custom fields (e.g. > the one we're using for "Type of work") *can* have multiple values > allowed, so we could possibly create another custom field and entirely > replace our usage of categories with it. However, I couldn't find how > one can fully disable the Category field, so it would be confusing. > > With this in mind, and my above note about the "field of expertise" > (sic, IMO), I think the best we can do is to: > > 1. use the Category field for generic, transversal type of issues > (e.g. accessibility, i18n, hardware support, persistence); > 2. create a dedicated custom field called "Subsystem" or "Affected > Tool" or similar. I really, really love this solution and think it would improve the situation :) Cheers, BitingBird _______________________________________________ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
