Tilted Forum Project Discussion Community - View Single Post - [PHP

Mephex · 02-27-2004, 12:10 PM

So you have a ticket that has been entered.

Are you assigning those tickets ? If so, problem solved, the responsible party updates/closes the ticket.

If not, maybe you should have techs take ownership of the ticket, so that only one tech/person can edit it at a time.

I, on the other hand, have a ticket system where it stacks the replies, similiar to a msgboard, until the ticket is closed. If Joe closes the ticket while frank is still updating, then frank goes to hit update, it returns with an error stating that this ticket was already closed by Joe.

Or, you could get complicated, and track sessions to pages to show that someone is currently viewing, then have a process that timesout inactive sessions.

I don't allow users to hit the back button, simply by replacing the last page in the users history with the current page being viewed, then as an extra measure, having all pages set to expire -1d.

Hope this helps, sounds like fun.

02-27-2004, 12:10 PM	#2 (permalink)
Mephex Psycho	So you have a ticket that has been entered. Are you assigning those tickets ? If so, problem solved, the responsible party updates/closes the ticket. If not, maybe you should have techs take ownership of the ticket, so that only one tech/person can edit it at a time. I, on the other hand, have a ticket system where it stacks the replies, similiar to a msgboard, until the ticket is closed. If Joe closes the ticket while frank is still updating, then frank goes to hit update, it returns with an error stating that this ticket was already closed by Joe. Or, you could get complicated, and track sessions to pages to show that someone is currently viewing, then have a process that timesout inactive sessions. I don't allow users to hit the back button, simply by replacing the last page in the users history with the current page being viewed, then as an extra measure, having all pages set to expire -1d. Hope this helps, sounds like fun.