<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
My 2 cents ...<br>
<br>
As a heavy user of custom multi-select combo boxes I find the current
design both very useful, flexible, & intuitive. While this
suggestion may be a simplification for those who need it, it impresses
me as a step backwards to a less useful, versitile, or powerful
arrangement. I find it very useful to be able to bulk add or delete
combinations of specific values in a single step.<br>
<br>
Bill Davis<br>
<br>
Stephen Turner wrote:
<blockquote cite="mid:6.2.3.4.2.20071206133633.04647458@po14.mit.edu"
type="cite">Hello,
<br>
<br>
We've finally gotten around to working with RT 3.6, and it's cool that
on the bulk update screen you can now update custom fields.
<br>
<br>
I'd like to make some suggestions about the interface for that, though.
I know it's subjective, but the "add values/delete values" scheme for
seems awkward and counter-intuitive. It's certainly different from the
single-ticket custom field update interface.
<br>
<br>
I'm thinking that users really think in terms of modifying a field
value, not adding or deleting values. In fact, 'Add values' seems to be
a misnomer - if you type something in there (or select something from a
drop-down) it replaces the current value, it doesn't add it to the
existing value.
<br>
<br>
For select fields, how useful is it to be able to delete specific
values? If I want to clear a custom field on any ticket where the value
is, say, 'Problem Report', I'm more likely to define my search to look
for such tickets, or simply define the tickets to be updated via the
checkboxes on bulk update.
<br>
<br>
Lastly, one major omission is the ability to just clear a select custom
field (set it to 'no value') for a list of tickets.
<br>
<br>
I've attached a screenshot of our implementation of bulk CF updates -
the interface seems simpler and more intuitive. We've added a 'null'
entry to drop-downs, marked by '------', which means 'don't update the
field'. This means that selecting 'no value' means "set the field to
'no value' on selected tickets". This behavior matches the
single-ticket update pages.
<br>
<br>
You can do everything else with this interface except 'set field to
no-value where current value is "foo"' - but as I describe above, this
would more likely to be done by limiting the search and/or checking
boxes.
<br>
<br>
Thanks,
<br>
Steve
<br>
<br>
<br>
Stephen Turner
<br>
Senior Programmer/Analyst - Client Support Services
<br>
MIT Information Services and Technology (IS&T)
<br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
List info: <a class="moz-txt-link-freetext" href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel</a>
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch today.
Email us at <a class="moz-txt-link-abbreviated" href="mailto:sales@bestpractical.com">sales@bestpractical.com</a> or call us at +1 617 812 0745.</pre>
</blockquote>
</body>
</html>