Forum OpenACS Q&A: tickets? known problem? (linux debian-2.2, acspg-3.2.2.b3, pg-7.0.2)

tickets? known problem? (acspg-3.2.2.b3, pg-7.0.2)

Hi...

I put up an acs at http://www.laney.edu:8080/ (also, one at http://mercury.laney.edu/ does the same thing) and the ticket tracker won't display the admin page. Here are some log entries:

Errors since 28/Jun/2000:17:07:05

[28/Jun/2000:17:21:52]
    Error: Ns_PgExec: result status: 7 message: ERROR:  parser: 
parse error at or near "("

    Notice: nsd.db: sql(localhost::communitylaneydb):  select
     ticket_issues.msg_id,
     ticket_issues.ticket_type,
     ticket_issues.one_line,
     ticket_issues.status,
     ticket_issues.severity,
     ticket_issues.posting_time,
     users.email,
     assigned_users.email as assigned_user_email,
     ticket_projects.title as project_title,
     ticket_projects.project_id,
     ticket_issues.priority,
     to_char(ticket_issues.modification_time, 'mm/dd/yy') as 
           modification_time_pretty,
     to_char(ticket_issues.posting_time, 'mm/dd/yy') as 
           creation_time_pretty,
     to_char(ticket_issues.close_date, 'mm/dd/yy') as 
           close_date_pretty,
     to_char(ticket_issues.deadline, 'mm/dd/yy') as deadline_pretty,
     to_char(sysdate - deadline) as pastdue,
     ticket_issue_assignments.active_p as assigned_p,
     ticket_issue_assignments.user_id as assigned_user_id,
     ticket_issues.public_p,
     ticket_priorities.name as priority_name
    from ticket_issues, ticket_priorities, ticket_projects, users, 
           ticket_issue_assignments, users assigned_users
    where ticket_priorities.priority = ticket_issues.priority
    and users.user_id = ticket_issues.user_id
    and ticket_projects.project_id = ticket_issues.project_id
    and ticket_issues.msg_id = ticket_issue_assignments.msg_id(+)
    and ticket_issue_assignments.user_id = assigned_users.user_id(+)
    and (exists (select msg_id from ticket_issue_assignments
    where ticket_issue_assignments.msg_id = ticket_issues.msg_id
    and ticket_issue_assignments.user_id = 3
    ))
    and ((status <> 'closed') and (status <> 'deferred'))

    order by ticket_issues.msg_id, ticket_issues.priority, 
ticket_issues.posting_time

[28/Jun/2000:17:21:52]
    Error: nsd.tcl: Database operation "select" failed (exception 
NSDB, "Query was not a statement returning rows.")
    Database operation "select" failed (exception NSDB, "Query was not 
                                      a statement returning rows.")
        while executing
    "ns_db select $db $query"
        invoked from within
    "set selection [ns_db select $db $query]"
        (file "/web/communitylaney/www/ticket/admin/index.tcl" line 
                                                                222)
        invoked from within
    "source $ad_conn(file)"
        (procedure "ad_handle_abstract_url" line 67)
        invoked from within
    "ad_handle_abstract_url cns614 {}"
    Notice: Running scheduled proc sec_sweep_sessions...
(end of log)

-Jim

Okay,  this is by no means an authoritative answer here,  but from looking around,  the ticket module has been superseded by the new-ticket module which is closely integrated with the BITS Setup (Bug and Incident Tracking System).

The only thing to note with new-ticket is that you should first setup a team in /team otherwise you will get Server Error pages loaded in your browser.  I think Ben is still working on the BITS portion prior to offical release of the openACS system.

Cheers

Yes, yes, I really need to document this. Ticket has been superseded by new-ticket in OpenACS. The upcoming release of OpenACS will automatically redirect you to /team if there are no existing teams, and is generally more bug-proof.