A user brought this issue up today, which I hadn't considered. This is using Trac 0.11dev, albeit a revision that hasn't been updated in a couple months. She has a report in which a custom multi-line text field (like description, just with a different name) is displayed as a separate row under each ticket, and wanted it included as a column in her CSV export of the report.
I pointed out to her that she could manually change the query string from row= to col= to include that field temporarily in a column for the sake of export. But it's still something of an inconvenience. I don't see why the export shouldn't take fields that are on their own row and just append them as a column. I just wonder if this is an oversight that would require a patch, or if this is for some reason intentional. I know that a plugin could also provide that functionality easily enough, but I'd prefer to avoid yet another plugin for something that seems to me like the expected functionality. I just wonder if I'm missing something. Erik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
