Tickets :: Comment on [#4928] Combine "Tickets which are" and "Type" selects in Search form

* Your Email Address
* Spam protection	Enter the letters below: __..__..__ .___.. , (__ \| \|[__) \| \./ .__)\|__\\| \| \|
Comment	> The "Tickets which are" select has two, related problems. First, the > ticket states shown are the Whups internal categories, which are not > directly exposed to the user elsewhere (unless your own states happen > to map 1:1 to those names). Second, you cannot make fine-grained > distinctions between the categorizations when you have multiple > "Assigned" states (eg states "Implement" and "Verify" are both > "Assigned"). > > > > The functionality of type and "tickets which are" can be achieved by > combining both into a table of multi-selects, one column for each > type. For example: > > > > Bug Enhancement Task > > ---------------- \| ------------------- \| ------------ .... > > Reported \| Requested \| ..... > > Open \| Open > > Fix \| Implement > > Verify \| Verify > > Deploy \| Deploy > > Resolved \| Finished > > > > With this construct, you can select multiple type and states in a > single motion. As an extension, clicking on the ticket type header > would select/deselect all the included states (or there could be an > explicit select/deselect all link).
Attachment
Watch this ticket