4 | | |
5 | | Replying to [comment:7 Ryan J Ollos]: |
6 | | > I've been thinking the main need to be addressed in this ticket is to hide components and version from the ticket form. For example, on this site we might want to hide versions that are no longer actively supported (Trac < 0.11). Therefore this is mainly about revoking permission to assign tickets to hidden components and versions. To address concerns about the length of the select we can implement autocomplete (comment:6). |
7 | | > |
8 | | > I've made some assumptions, which should be debated: |
9 | | > * The Query module will show all Components and Versions. |
10 | | > * The Ticket page will show all Components and Versions if the users has `TICKET_ADMIN`. This behavior is similar to Milestones: completed Milestones are shown if the user has `TICKET_ADMIN` |
11 | | > * I chose //Hidden// as the field label to try and be unambiguous. However, since the items aren't hidden everywhere, maybe a term like //Archived// would be more appropriate. |
12 | | > |
13 | | > I'm considering: |
14 | | > * Adding dynamic functionality to toggle the hidden parameter from the admin listing page. This will make it easier to change the hidden state of many items. |
15 | | > * For users with `TICKET_ADMIN`, group hidden and non-hidden items (like what's done for Milestones in grouping open-with-due-date/open without-due-date/closed). |
16 | | > |
17 | | > Work in progress: log:rjollos.git:t11637_hide_version_and_components. |