Tickets: Ways to get tickets inputed into the system?
Page: 1
Recent posts in this topic
Ideally what I would like to see (I haven't purchased AC1.0, would like to know if this is here) is that unauthed users could create tickets either via email or via a webform. On the webform tickets could be sent to a number of projects and then would be notified on status of the ticket. Essentially integrating something like eTicket into AC. That alone might get me to jump from using eTicket and AC0.71 to AC1.0
Pro
I don't think I have seen anything like this in the demo... it would seem to me this is the kind of feature best served by a custom module, using the API.
There is a ticket system in the corporate version, but to my knowledge it's not possible to post via email...
There is a ticket system in the corporate version, but to my knowledge it's not possible to post via email...
The best way to predict the future is to invent it
------------------------------------------
Apache 2.2.8 - MySQL 5.0.45 - PHP 5.2.6 | Debian 4.0 (Etch)
------------------------------------------
Apache 2.2.8 - MySQL 5.0.45 - PHP 5.2.6 | Debian 4.0 (Etch)
If I knew anything about the API yet, I'd look into how easily this could be done with a simple form page that interacts with the API. That would be a cool feature.
Staff
Ilija Studen
on Oct 8. 2007. 9:00 pm
Tickets can be created only through activeCollab, but a plugin can be created to insert them through publicly accessible form.
We use something similar to create you accounts in the demo. Instead of tickets we are creating companies, users and projects. I'll work on development documentation as soon as launch pressure is gone. Maybe this one would be a good and practical example that I could use for a tutorial? :)
Thanks
We use something similar to create you accounts in the demo. Instead of tickets we are creating companies, users and projects. I'll work on development documentation as soon as launch pressure is gone. Maybe this one would be a good and practical example that I could use for a tutorial? :)
Thanks
activeCollab Team Member
Oooh yes - tickets would be excellent for my scenario also - we have a small webteam in a rapidly expanding company (100+) - we need other depts to be able to submit a ticket for web changes/requests and for the tickets to be visible in Activecollab - perhaps even some automated task/project creation...
I have a demo account but haven't had a proper play yet, so sorry no solid feedback yet.
I have a demo account but haven't had a proper play yet, so sorry no solid feedback yet.
justinbest
on Oct 9. 2007. 4:20 pm
Easy ticket creation is probably the #1 most important feature for me. I run an IT services company with several technicians. We use BaseCamp currently, but are needing some features that just are not provided. I'm ready to spend $400 in a heartbeat, plus $200 per year, if I can get my needs met.
An initial examination of aC would indicate that it has what BaseCamp is missing (for me). Except e-mail ticket creation and subscription. I would like the ability for my users to send email, on a project-by-project basis, to an email (or addresses) within my organization, which in turn creates tickets. Example:
from: someone@mycustomer.com
message: "my printer won't work! help!"
sent to: support-project1@mycompany.com
attchment: screenshot.jpg
This creates a ticket in project1 which can then be assigned to a tech for completion. Not all projects would have ticket request emails (some projects would need to have tickets created manually, or optionally have a "catch all" project from which tickets could be re-assigned to the appropriate customer)
Bonus points: Once completed, it would be nice to optionally send the case notes to the original creator (someone@mycustomer.com) detailing what was done to fix the problem.
An initial examination of aC would indicate that it has what BaseCamp is missing (for me). Except e-mail ticket creation and subscription. I would like the ability for my users to send email, on a project-by-project basis, to an email (or addresses) within my organization, which in turn creates tickets. Example:
from: someone@mycustomer.com
message: "my printer won't work! help!"
sent to: support-project1@mycompany.com
attchment: screenshot.jpg
This creates a ticket in project1 which can then be assigned to a tech for completion. Not all projects would have ticket request emails (some projects would need to have tickets created manually, or optionally have a "catch all" project from which tickets could be re-assigned to the appropriate customer)
Bonus points: Once completed, it would be nice to optionally send the case notes to the original creator (someone@mycustomer.com) detailing what was done to fix the problem.
