Menu
▾
▴
#4 External Ticket Input
A way of entering tickets/artifacts on a single form
without user level authentication.
The idea: Allow entertrack to be somewhat integrated
with another web application (such as an internal
groupware site). This sight could pre-populate an
authentication code (so that not everyone on the
internet can enter tickets), but the user contact info
(name and email address) is filled in by the web app.
This would allow users in a company to enter tickets
without having to actually have accounts in EnterTrack.
Thus avoiding dual-signon, and/or complicated
integration of authentication stores.
Ideally, the system would communicate with ticket
creator via email regarding the status changes of the
ticket.
Initial implementation would only need to be a basic
form. Categorization of tickets could then be done by
the EnterTrack techs or admins.
Logged In: YES
user_id=7446
This is waiting on further API development of of EnterTrack. At some
point, it will be pretty easy to create another top-level script (like index.php
or email.php) which provides this API. It may be easiest to implement this
in XMLRPC, for the sake of portability.
This would be a good project for someone new EnterTrack -- use email.php
as an example, and just get it to create new issues. We can build from
there.
Logged In: YES
user_id=7446
Take a look at the new notification system -- http://sourceforge.net/tracker/
index.php?func=detail&aid=1265318&group_id=126639&atid=706388 -- it
contains much code cleanup around issue creation and event submission. We
could create another top-level script like email.php (perhaps xmlrpc.php or
xoap.php?) that can handle requests like these using some standard protocol
(a protocol implemented by PEAR, preferably).