...
- the register of names needs to use only the latest date if there are multiple lines; how to do that? try a pivot table that filters the maximum value only, and do the inquiry against that.
- have the spreadsheet understand which survey invitation string to use; make a long set of upload commands that work from a single directory and not subdirectories...
- receive the survey transactions into a spreadsheet and divide it up by queue and autogeneate the reports across muliple worksheets. Simpler is better. (Process of letting go)
Hmmm...
The only useridentifiable info that comes through in this way is the kerberos username of people. What if that's not their email? (Actually, how will RT know the email-to-kerberos relationship if that isn't their name? Hmmm. It won't catch the tickets with more than one name in the requestor field.
It's possible that these limitations are too dire to allow switching to RT for ticket selection. Hmmm, indeed!
...
The using-Brio query...
Based on the inside-RT queiries documented below, a reasonable Brio query for RT tickets to survey would include these queues:the following queues. Running this in Brio for 6/8 to 6/15/2009 yielded 593 tickets.
Software::Licensing,
Software::Licensing::Filemaker
Software::Licensing::Mathematica
Software::Licensing::RHEL
Software::Licensing::Questions
Software::Matlab::Billing
what to do about Subject NOT LIKE "Maple" ?
...