[rt-users] RT For an ISP

[Ben Robson]

This link might be of help: http://www.htmlhelp.com/reference/html40/forms/input.html
 
You should be able to (and note I havn't checked this at all) modify the code that shows the ticket creation form and set the READONLY flag on the <INPUT> box for the Requestor.
 
That way the requestor, autofilled, gets displayed, but the user can't edit it.
 
The other way would be to edit the same code, just don't display the $ticket->requestor (not actual syntax) value in a pre-completed <INPUT> box, just display it as text instead.
 
So if the code said <INPUT NAME=requestor VALUE=$ticket->requestor>  change this to just be <B>$ticket->requestor</B> thus removing the ability to change the value.
 
BenR

________________________________

From: rt-users-bounces at lists.bestpractical.com on behalf of Jason Fenner
Sent: Wed 22/02/2006 2:31 AM
To: Mustafa Badawi
Cc: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] RT For an ISP



Have you found a fix for this yet?

Mustafa Badawi wrote:

>Dear All
>
>I am trying to use RT for my dialup clients. I only want my clients to use
>the web interface to create tickets and not the email interface. I have
>created an unprivileged RT account for each of my users. The problem I have
>is that when the user logs on and selects the queue I have provided he/she
>can enter any value in the requestor field thus automatically creating a new
>user as a watcher. The rightful requestor of the ticket (the account I have
>created) cannot actually view the new ticket because he/she has no
>permission to view it.
>Is there a way of forcing the requestor to be the RT account I have already
>created! Keeping in mind that I do not want users seeing all the tickets in
>the queue - only their own tickets.
>Any hints would be greatly appreciated
>
>Mustafa Badawi
>
> 
>
>------------------------------------------------------------------------
>
>_______________________________________________
>http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
>Be sure to check out the RT Wiki at http://wiki.bestpractical.com
>
>Download a free sample chapter of RT Essentials from O'Reilly Media at http://rtbook.bestpractical.com
>
>WE'RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
>San Francisco - Find out more at http://bestpractical.com/services/training.html
>


_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Download a free sample chapter of RT Essentials from O'Reilly Media at http://rtbook.bestpractical.com

WE'RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
San Francisco - Find out more at http://bestpractical.com/services/training.html


............................................................................................................................

This email (including all attachments) is intended solely for the named addressee. It is confidential and may contain legally privileged information. If you receive it in error, please let us know by reply email, do not disclose any information contained in it, delete it from your system and destroy any copies. This email is also subject to copyright. No part of it should be reproduced, adapted or transmitted without the written consent of the copyright owner. Emails may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems.

We give no warranties in relation to these matters. If you have any doubts about the authenticity of an email purportedly sent by us, please contact us immediately.  Privacy - Please be aware that information provided in response to this email may contain personal information, which Classic Blue may collect, and use for the purposes of marketing information technology products and services to you.  For further information regarding Classic Blue's privacy policies please refer to www.classicblue.com.au
............................................................................................................................
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20060222/802984de/attachment.htm>