ticket-system

I am creating my own system to managing all tickets which are comes from freshdesk.com through its API. I am making curl request to fetch data from freshdesk.com. With getting data of related to tickers its works fine but when i am requesting for all users through curl request then its give me error: Warning: curl_errno(): 2 is not a valid cURL handle resource in C:\wamp\www\test.php on line 28. My code is like that: $ch = curl_init(); $cOption = array( CURLOPT_URL => 'http://velocity.freshdesk.com/contacts.xml', CURLOPT_HEADER => 0, CURLOPT_USERPWD => "$email:$password", CURLOPT_POST => false

I've been working with SVN for a couple of years and recently been working on some projects involving Trac. It might seem odd for most of you but I come from design oriented background where those tools are not so often used. For the moment we mostly use Basecamp to keep track of client requirements, documents etc. And on the other hand SVN for source control (between developers only). So, the aim being to integrate Trac to the bundle (and maybe other helpful features) I've been looking around for an online environment that could fulfill these requirements. There's a lot out there but my main

I am building a basic support request system where the customer can log in and ask a question and an admin can go in and reply and it will set the status to "Responded" and e-mail the customer to let them know someone has responded. My question is.. I have a "comments" section which is a log of the interaction between the admin and the customer. If I e-mail the customer the initial response from the admin, then I have a feeling they will just hit "Reply" from their email and start communicating through there, and the logs won't be stored. I could either e-mail the customer and say "Log in to

I'm building a ticket-selling application which tracks an inventory of tickets, de-activating them when a particular ticket is sold out. I'm wondering what the best practice is for releasing inventory back into the store when an order is abandoned mid-way through. The current flow: Users add items to an order as line_items and the order is marked as completed on successful payment items has a quantity_available that's updated based on their line_items I sweep periodically for orders with no action in > 20 minutes, delete those orders' line_item s and update the quantity_available It feels like

Is there a free support ticket product like osTicket? I would want it not to be bloated with features, since I want to be able to use it without having to get into it a lot. I've looked into this quite a bit, and here are some of the best options I found. For reference, my choice was HelpSpot for the overall, but SupportTrio has an excellent offering, and there's a completely free version (limited number of users). Free Software SupportTrio (free or paid versions available) Demo here Nice web interface Knowledgebase included direct email to email communication, decent interface, free version

Is there a more full featured ticketing system than Github provides, but that integrates with Github issues? The pull request feature, as well as others, are great about Github, but I feel some issues/projects need more (like prioritization, attachments, and custom issues/ticket setup.) waffle.io uses a simple kanban-like UI to organize existing GitHub issues, and with some plans can eve ndisplay priorities made on the site on GitHub's issue tracker. It is very simple though, so it may not be enough if you need anything more than kanban-style priorities on GitHub issues. GitHub just got closer