
| Key: |
CHD-1993
|
| Type: |
Improvement
|
| Status: |
Open
|
| Assignee: |
Unassigned
|
| Reporter: |
Joe Geck
|
| Votes: |
0
|
| Watchers: |
0
|
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
|
|
Environment:
|
4.3.1/5.x
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is duplicated by:
|
|
CHD-2426
exported csv improvements
|
|
|
|
|
|
Summary:
I cannot believe this isn't already in JIRA but I can't find it (you'd think whoever filed it would have used the word "export"...) In any case, there's no great way to convert the group, bucket, ... , worker IDs into the "english" when you use the 'export' from any worklists. I assume there's no workaround?
Steps:
0) User reported it with Opportunities and workers, but you could do it from any ticket list too.
1) From 'Overview', click 'export' and expose some of the "ID" columns: group, bucket, last (next) worker, etc.
2) Choose CSV or XML and click 'Export'.
Result:
Notice results are IDs instead of english, i.e. "Last Worker" = 647
|
|
Comment by Joe Geck [30/Jul/10 01:17 PM]
This is because it's the views/worklists which translate the raw data into human-readable form.
When you export for scripting purposes, the raw data is what you actually want. We could add a toggle.
In 5.2 I plan to add 'renderers' to views, which would allow you to format a cell in human readable format regardless of where we're displaying it: worklists, RSS, export, etc.
|
|