Forum OpenACS Q&A: ticket-tracker
customer care type sytem using ticket-tracker and workflow on
1. Is there an existing way for users to have only certain tickets
viewable? For example: clients can only see tickets pertaining to
their company (a group). Seems like I will have to modify some.
2. What is the difference between ticket-tracker and wf-ticket-
tracker? I tried installing wf-ticket-tracker but couldnt get it
working. I get the same error already reported for that module
(1398). Just wanted to make sure I was going forward with the correct
Here are my answers:
1. You mount different instance of ttracker for each company or group.
2. wf-ticket-tracker I believe will be dropped, not sure though I hope someone can post a definite answer here.
What I was working on was adding a groupid field to the tickets and sort by that for customer views. What do you think?
I think using permissions, relationships and groups may be less scalable than using the package awareness of OpenACS applications. Please have a look at the data model of OpenACS and ticket tracker. Unless you want a very granular security model I suggest not to use grouping and permissions on the ticket level.
Regarding the central administration of the tickets you may want to create some custom pages that will show you tickets regardless of package_id.
My approach is like removing rather than adding functionality.
The only point of writing it was as an example of how to use workflow with your package. It was never meant to be used for anything past that.
Now that there's real ticket-tracker (not-lite), it should be removed from the repository.
2. Does ticket tracker utilize workflows?
Ticket Tracker makes use of workflow. Ticket Tracker Lite does not use workflow. Workflow ticket tracker I believe will be junked out later.