make Keywords field optional

[wkornew]

It is very annoying that the Keywords field takes up screen space even if it's not needed. I know that it has been requested by many people, but I'm sure that there are even more people who don't use it, at all. Please make it optional.

Why is it not possible to make the Keywords field one of those [TracTicketsCustomFields]?

[wkornew]

please patch ticket/api.py

[wkornew]

BTW, the patch is for V0.9.5. ;)

[wkornew]

cleaned up. includes documentation for show_keywords. patch against trunk

[wkornewald <wkornewald>]

So, will nothing happen with this? Will it be fixed with the workflow branch?

[Noah Kantrowitz <coderanger@…>]

The SimpleTicket plugin already fixes this. You can hide whatever fields you want.

[Waldemar Kornewald <wkornewald>]

Actually, I wanted a less hacky solution (SimpleTicket? requires having a new permission policy, etc.). Keywords could be implemented with custom fields or is there special code for them somewhere?

[Noah Kantrowitz <coderanger@…>]

Replying to Waldemar Kornewald <wkornewald>:

Actually, I wanted a less hacky solution (SimpleTicket requires having a new permission policy, etc.). Keywords could be implemented with custom fields or is there special code for them somewhere?

SimpleTicket does not require anything related to the security branch, it runs on plain ol' 0.10.x.

[Waldemar Kornewald <wkornewald>]

No, I meant that you must give people a new permission (SIMPLE_TICKET or something like that).

[ilias@…]

you can verify this issue from the tracx plugin (on top of 0.11dev), which goes a step further to provide different ticket-fields for different ticket-types.

Once implemented, this should cover your needs.

sidenot: stable versions get only 'bugfixes'. So, your patch (functionality) provided for 0.9.5 will most possibly not be applied (= 'wontfix').

To team: this issue should be generalized ('make ticket fields optional', for 0.11dev) or alternatively closed as 'wontfix', as it affects an old release.

[Waldemar Kornewald <wkornewald>]

Just to clarify. This has the problem that TRAC_ADMIN and TICKET_ADMIN still have access to the keywords field. I can provide a new patch (for 0.10 or 0.11), of course, but the real solution would probably be to remove the field completely. It's not needed everywhere, anyway. This should probably be implemented with a generic "tag" plugin which also allows for showing tag clouds. At least, this field isn't used by everyone and Trac should only provide the greatest common denominator. The rest should be done with modules or custom fields. IMHO, of course.

[cboos]

Thinking about #2464 and its generalization to conditional custom fields, I wonder if that could not be extended to regular fields as well (and anyway, the difference is blurred in the GenericTrac proposal).

In this view, the precondition for the Keyword: field could simply be false, so that it'll never apply.

In a similar way, the th:SimpleTicketPlugin effects could be obtained by having tests for the permissions in the precondition.

[cboos]

#5078 was another request for the same feature.

[asloan12@…]

adding my request for this change, we don't need the Keywords field and would like to be able to make it disappear. Thanks