<?xml version="1.0" encoding="UTF-8"?>
<user>
  <id type="integer">122703</id>
  <url>http://uservoice.com/users/122703-mwolfe</url>
  <avatar_url>http://www.gravatar.com/avatar/9615ebe96dc1019fd3bb91ec41472cc2?default=http://uservoice.com/images/icons/default-avatar.jpg</avatar_url>
  <display_name>mwolfe</display_name>
  <name deprecated="true">mwolfe</name>
  <username deprecated="true">mwolfe</username>
  <activity_score type="integer">51</activity_score>
  <idea_score type="integer">22</idea_score>
  <supported_suggestions type="array" deprecated="false">
<suggestion>
  <id type="integer">68344</id>
  <url>http://bigwebapps.uservoice.com/pages/3268-new-features/suggestions/68344-add-tagging-to-tickets</url>
  <title>Add &quot;tagging&quot; to tickets</title>
  <abstract>Such as with flickr and other websites.. if we are having a common issue we can tag a series of tickets with that issue such as &quot;XYZ Database Error 44.&quot;  Then when we resolve that issue, we can easily ...</abstract>
  <text>Such as with flickr and other websites.. if we are having a common issue we can tag a series of tickets with that issue such as &quot;XYZ Database Error 44.&quot;  Then when we resolve that issue, we can easily view that tag and close out all of those tickets, or look at the other tickets to see what information is common to them all to possibly help diagnose it.  Another example would be a tag for &quot;Confirmed bad monitors&quot; - that way we could quickly pull up which tickets need monitor replacements without going into every ticket in the monitors class to see which we have confirmed as actually bad and which we haven't.  Allow multiple tags would be helpful.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">19</vote_count>
  <comments_count type="integer">0</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">3268</id>
    <name>New Features</name>
    <key deprecated="true">general</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">122703</id>
        <display_name>mwolfe</display_name>
        <name deprecated="true">mwolfe</name>
        <username deprecated="true">mwolfe</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2008-11-11T19:52:51Z</created_at>
  <updated_at type="datetime">2008-11-11T19:52:51Z</updated_at>
  <page deprecated="true">
    <key>general</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">69503</id>
  <url>http://bigwebapps.uservoice.com/pages/3268-new-features/suggestions/69503-having-vip-option-on-help-tickets</url>
  <title>Having VIP option on Help Tickets</title>
  <abstract>I'd like there to be an option to escalate help tickets for a VIP.

If a VIP of an organization calls in a help ticket, it's priority gets escalated by default, and/or be assigned to a technician or ...</abstract>
  <text>I'd like there to be an option to escalate help tickets for a VIP.

If a VIP of an organization calls in a help ticket, it's priority gets escalated by default, and/or be assigned to a technician or tech pool.  This way, a VIP can get help ASAP.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">19</vote_count>
  <comments_count type="integer">2</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">3268</id>
    <name>New Features</name>
    <key deprecated="true">general</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">127227</id>
        <display_name>fanzivino</display_name>
        <name deprecated="true">fanzivino</name>
        <username deprecated="true">fanzivino</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2008-11-12T16:05:29Z</created_at>
  <updated_at type="datetime">2008-11-12T16:05:29Z</updated_at>
  <page deprecated="true">
    <key>general</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">75229</id>
  <url>http://bigwebapps.uservoice.com/pages/3268-new-features/suggestions/75229-add-date-time-field-for-last-entry-in-a-ticket-to-list-view-</url>
  <title>Add date/time field for last entry in a ticket to list view.</title>
  <abstract>Add an optional field in the ticket view that shows the time and date of the last entry in a ticket.  This would be helpful for sorting to tell which tickets haven't been tended to recently.

We...</abstract>
  <text>Add an optional field in the ticket view that shows the time and date of the last entry in a ticket.  This would be helpful for sorting to tell which tickets haven't been tended to recently.

We work on a site rotation and could use this to quickly tell which tickets we have already worked on for that site on a particular day and which we still need to look at.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">9</vote_count>
  <comments_count type="integer">0</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">3268</id>
    <name>New Features</name>
    <key deprecated="true">general</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">122703</id>
        <display_name>mwolfe</display_name>
        <name deprecated="true">mwolfe</name>
        <username deprecated="true">mwolfe</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2008-11-20T17:31:20Z</created_at>
  <updated_at type="datetime">2008-11-20T17:31:20Z</updated_at>
  <page deprecated="true">
    <key>general</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">82733</id>
  <url>http://bigwebapps.uservoice.com/pages/3268-new-features/suggestions/82733-allow-technicians-to-transfer-tickets-on-hold-to-new-queue</url>
  <title>Allow technicians to transfer tickets on hold to new queue</title>
  <abstract>Right now, when a technician transfer a ticket on hold to the new tickets queue it sets the status back to open.

We would like to be able to place a ticket on hold and transfer it back to the...</abstract>
  <text>Right now, when a technician transfer a ticket on hold to the new tickets queue it sets the status back to open.

We would like to be able to place a ticket on hold and transfer it back to the queue.  Often times there will be an approval pending or some action that we are waiting on someone to complete before we can do anything further with it.  We don't neccessarily need to hang onto the ticket ourselves during this time.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">3</vote_count>
  <comments_count type="integer">0</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">3268</id>
    <name>New Features</name>
    <key deprecated="true">general</key>
  </forum>
  <response nil="true"></response>
  <created_by>
    <supporter>
      <user>
        <id type="integer">122703</id>
        <display_name>mwolfe</display_name>
        <name deprecated="true">mwolfe</name>
        <username deprecated="true">mwolfe</username>
      </user>
    </supporter>
  </created_by>
  <created_at type="datetime">2008-12-02T19:36:03Z</created_at>
  <updated_at type="datetime">2008-12-02T19:36:03Z</updated_at>
  <page deprecated="true">
    <key>general</key>
  </page>
</suggestion>
<suggestion>
  <id type="integer">138308</id>
  <url>http://bigwebapps.uservoice.com/pages/3268-new-features/suggestions/138308-custom-fields-specific-to-class</url>
  <title>Custom Fields specific to Class</title>
  <abstract>When a user creates a new ticket and they select a problem type, ask users questions specific to that issue and record the responses.

This would work best when configurable by the site...</abstract>
  <text>When a user creates a new ticket and they select a problem type, ask users questions specific to that issue and record the responses.

This would work best when configurable by the site technicians/administrators (as opposed to a generic set of questions across all bigweb clients).

It would also be useful to help the helpdesk staff get information that the on-site technicians need.</text>
  <closed_at nil="true"></closed_at>
  <vote_count type="integer">6</vote_count>
  <comments_count type="integer">0</comments_count>
  <status nil="true"></status>
  <forum>
    <id type="integer">3268</id>
    <name>New Features</name>
    <key deprecated="true">general</key>
  </forum>
  <response nil="true"></response>
  <created_at type="datetime">2009-03-11T14:00:52Z</created_at>
  <updated_at type="datetime">2009-03-12T17:22:11Z</updated_at>
  <page deprecated="true">
    <key>general</key>
  </page>
</suggestion>
  </supported_suggestions>
  <created_at type="datetime">2008-11-11T19:44:25Z</created_at>
  <updated_at type="datetime">2009-06-02T15:07:54Z</updated_at>
</user>
