| Key: |
CHD-1180
|
| Type: |
New Feature
|
| Status: |
Open
|
| Assignee: |
Unassigned
|
| Reporter: |
Joe Geck
|
| Votes: |
0
|
| Watchers: |
1
|
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Related To
|
|
This issue is related to:
|
|
CHD-1179
[Custom Fields] Auto-complete support
|
|
|
|
|
|
|
| Value: |
2 - Significant Value
|
| Marquee: |
Custom Fields, Usability
|
Summary:
http://www.cerb4.com/forums/showpost.php?p=9679&postcount=1
[Worklists] Ability to edit values in place such as custom fields. This request was filed by the same person and goes hand-in-hand with another request
CHD-1179 [Custom Fields] Auto-complete support
(quote)
When we built suggestion 1 for our system, we made it we you could click on the field value in any ticket list view and the autocomplete editor would appear and let you choose a new value. In other words - you can edit the value IN PLACE on any list view.
It seems to me that this would be a huge improvement to the overall usability if the custom fields (and maybe other things?) could be edited in-place right from the list views. For instance, being able to click on the "next action" field and edit the value without having to click-popup-save.
(end quote)
|
|
Comment by Joe Geck [14/Apr/09 08:57 PM]
More details from pk4 in the same thread:
(quote)
It really is a time-saver for us. We use the custom fields for assignment to both billing account and project milestone. Letting people edit them in-place allows them to quickly go down a list of tickets and see which ones are not properly categorized - and assign them very quickly and easily.
RE: how did we do it (in case anyone cares)
We just assigned a custom class to the custom field column and attached a global listener that listens to onClick for objects with that class name (very minimal template mod). When you click on a value, the listener determines the custom field type from the class and replaces the displayed value with the appropriate editor widget. When it's done, the ajax calls are made to update the ticket and everything put back to normal.
(end quote)
|
|
