Forum OpenACS Q&A: Intranet Ticket Creation Problem.

Collapse
1: Intranet Ticket Creation Problem.
Posted by Chris Hardy on 08/13/00 05:30 PM
Welp, I'm in the middle of bug killing in the Intranet Module, and the
latest problem I've found is that it appears that the new-ticket
module was never set up to called from /intranet .. I'll keep on
working on it, but does whoever created /new-ticket know if I'm
barking up the wrong tree? (/intranet was calling
/new-ticket/admin/project-edit.tcl, which does not exist)
Collapse
2: Response to Intranet Ticket Creation Problem. (response to 1)
Posted by Ben Adida on 08/13/00 05:35 PM
No, you're barking up the right tree, but new-ticket is significantly different from ticket (read "better," hopefully). The idea is that you should create a team (a row in ticket_project_teams) for each Intranet group (map it directly to the user-group of your Intranet client), and then send over to /new-ticket/project-top.tcl?project_id=$project_id. There is no separate admin section anymore in new-ticket, it is all handled in the same pages (a solution I vastly prefer).
Collapse
3: Response to Intranet Ticket Creation Problem. (response to 1)
Posted by Chris Hardy on 08/13/00 11:24 PM
Ok, so, I need to have /intranet/projects/ticket-edit.tcl insert the project_id into ticket_project_teams and then redirect over to project-top.tcl?
Collapse
4: Response to Intranet Ticket Creation Problem. (response to 1)
Posted by Ben Adida on 08/13/00 11:28 PM
yes, with an obvious check to make sure you don't create a second team for a project. In fact, you'll probably need a nice "select for update" in there to make sure that a double-click doesn't create two teams.
Collapse
5: Response to Intranet Ticket Creation Problem. (response to 1)
Posted by Chris Hardy on 03/15/01 01:18 AM
Woo hoo! I've now got the Intranet module talking with the new-ticket module!