<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'><font class="Apple-style-span" size="3">Hi Fred,</font><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; "><br></div><div><font class="Apple-style-span" size="3">We use RT. It is written in Perl. I know Perl from years back. You can customize it at a lot of different levels. For example it has a custom fields configuration that you can apply to tickets, transactions, queues, etc (think CCK). We have written custom plugins and integrated it into our accounting system, Adempiere. A process we are continuing to mold an shape as we grow and scale. We have separate schema's in our posgresql database. We wrote a JAVA process into Adempiere to pull in our tickets per customer into invoices for automated billing.</font></div><div><font class="Apple-style-span" size="3"><br></font></div><div><font class="Apple-style-span" size="3">It is a swiss army knife when it comes to a ticketing system. You can easily do number 1. You either comment on a ticket which is an internal dialog that doesn't get sent to the customer, or replies which is correspondence with the customer. Number 2 works, but we disabled HTML. We were building reports from the transactions with time on it for our customers in Jasper. Having some with and without HTML made the reports look like garbage. Something that COULD be fixed, but we took the easy approach. Attachments we use quite frequently. As far as number 3. They can create tickets without logging in. They can correspond via email. But if you want them to log in then need a username and password. I could foersee being able to write software that lets people click a link to login as themselves. But the security ramifications would need to be thought through.</font></div><div><font class="Apple-style-span" size="3"><br></font></div><div><font class="Apple-style-span" size="3">I can't say I love RT. I love what we have done with it to make our business run smoother. At this point I learned the system and know how to make it do what I want to do. But it isn't a quite and easy setup. You do need to customize it to your needs. </font></div><div><font class="Apple-style-span" size="3"><br></font></div><div><font class="Apple-style-span" size="3">Talk to me offline if you are interested in having me do a crash course or setup for you. </font></div><div style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 12pt; "><br>----- "Fred Jones" <fredthejonester@gmail.com> wrote:
<br>> From: "Fred Jones" <fredthejonester@gmail.com><br>> To: "A list for Drupal consultants and Drupal service/hosting providers" <consulting@drupal.org><br>> Sent: Monday, December 12, 2011 2:23:37 PM GMT -05:00 US/Canada Eastern<br>> Subject: [consulting] Ticketing Software<br>><br>> I work with a small firm and the support system they have in place is<br>> no longer sophisticated enough for their growing needs. We are looking<br>> for an open source ticketing system, ideally in PHP. Integration with<br>> Drupal would be nice, but this is not a crucial need. The main issues<br>> are:<br>> <br>> 1. Two-way Email Updates: Both the client and the staff should be able<br>> to receive and send updates to tickets via email<br>> 2. Attachments and HTML Email: Ideally the email-based updates will<br>> allow users to send attachments and also HTML email. Many of our<br>> clients send HTML emails, with a bit of formatting, and so we need to<br>> be able to see that in the tickets, ideally.<br>> 3. Clients should not be required to create user accounts and login in<br>> order to access tickets.<br>> <br>> I think those are the main issues.<br>> <br>> Of course there is http://otrs.org/ but I can't readily see if they<br>> have the 3 features (or even 2) that we want. I have used Trac and<br>> OpenAtrium, but they both require logins. I found this<br>> http://www.bestpractical.com/rt/ that has email ticket creation but I<br>> don't know anything about it. I'm guessing http://www.zentrack.net/ is<br>> good and I think that's what I will try next.<br>> <br>> Basically what we *think* we want is that clients can submit our<br>> Contact Us form or email us at support@somefirm.com and either way, a<br>> ticket will be created in the system, we get updated via email and<br>> then we could reply via the web site or email and either way, the<br>> client would then be updated.<br>> <br>> Our needs are fairly simple, beyond those mentioned. Simple status of<br>> tickets so can close them etc.<br>> <br>> If anyone has any suggestions, or further ideas I should be<br>> considering, I would appreciate it.<br>> <br>> Thanks,<br>> Fred<br>> _______________________________________________<br>> consulting mailing list<br>> consulting@drupal.org<br>> http://lists.drupal.org/mailman/listinfo/consulting<br>> <br><br>-- <br><div><span class="Apple-style-span" style="border-collapse: separate; font-size: medium; "><span class="Apple-style-span" style="font-size: 16px;"><font style="font-family: 'times new roman','new york',times,serif;" size="5"><span style="background-color: rgb(255, 255, 255); color: rgb(255, 0, 0);">xforty technologies</span></font><br style="background-color: rgb(255, 0, 0); color: rgb(255, 0, 0);">Christian Pearce<br>888-231-9331 x1119<br><a href="http://xforty.com/">http://xforty.com</a></span></span></div><br></div></div></body></html>