Forum OpenACS Q&A: New-ticket

Collapse
1: New-ticket
Posted by Roberto Mello on 05/03/00 05:31 PM
I think I asked this before, or I thought of asking at least.

    I have new-ticket running, but how do you add a project to it ? I
couldn't find how to do it in the admin pages.

    Thanks,

    Roberto
Collapse
2: Response to New-ticket (response to 1)
Posted by Ben Adida on 05/03/00 05:42 PM
This is badly documented, sorry about that. In fact, I'm still
improving this piece of it. Go to /team and create a new team.
Each team corresponds to exactly one project in the ticket
tracker.

For more info go to https://openacs.org/doc/bits.html, where BITS
means (Bug and Issue Tracking System).

Collapse
3: Response to New-ticket (response to 1)
Posted by Roberto Mello on 05/03/00 09:19 PM

I am getting an error when trying to create a new team. PostgreSQL complains about referential integrity when team_add (I think) calls add_user_group saying that the group we're trying to create does not exist in user_group_types.

This may be because I am still running beta 2 (planning on upgrading this week, as soon as I finish the upgrade.sql, ugh!) but it brings me some questions:

  1. Why does the team manager need to create a new user group? Wouldn't it be easier to group scope it using an existing ACS group ? That way we'd have one more group scoped module, making administration easier.
  2. For every team created, a new group_type is created ?
  3. Can I create a "public" project ? One that everyone would be able to post issues. But how if, in order to do have new project I need a team and add people to the team ?

Thanks,

Roberto Mello

Collapse
4: Response to New-ticket (response to 1)
Posted by Ben Adida on 05/03/00 09:22 PM
the new ticket is not perfect. It could be improved. for example,
yes, it could be open to anyone submitting a ticket.  That
shouldn't be too hard to implement. It could also be scoped to an
existing group if you really wanted to, but I think that gets way
messy.

The bug you have is a beta2 problem, fixed by adding the
group_type "team"