BitingBird wrote:
>>> 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.
That would be great.
>> 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 :)
I'm not 100% convinced by the taxonomy of those two fields. But I'm very
happy to start with something that looks reasonable like this. I'm fine
with their names ("Category" and "Affected tool"). And we will surely
adjust their content later on as needed.
--
sajolida
_______________________________________________
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.
