Prevent change of CustomField per Queue

Hello,

is there a way to prevent users from changing a CustomField depending
on the queue?
I have a CF, which should be editable in queue A.
During the process, the ticket changes its queue to queue B.
There, the CF should only be visible, but NOT editable.

I tried to realize this with some scrips. My best result yet was
a scrip-loop, changing the CF value over and over :stuck_out_tongue:

My current ideas:

  • temporary changing the user rights
  • somehow interrupt the transaction
  • changing the CF back to its old value

Kindly regards,

Andreas Putzo

Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner

Hello,

is there a way to prevent users from changing a CustomField depending
on the queue?
I have a CF, which should be editable in queue A.
During the process, the ticket changes its queue to queue B.
There, the CF should only be visible, but NOT editable.

I tried to realize this with some scrips. My best result yet was
a scrip-loop, changing the CF value over and over :stuck_out_tongue:

My current ideas:

  • temporary changing the user rights
  • somehow interrupt the transaction
  • changing the CF back to its old value

Does the user need to edit the ticket when it is in queue B?
If not, then there should be no problem.

If so, the easiest way might be to create two custom fields with
the same name, and apply one to queue A (read/write) and the
other to queue B (read only). Then write a queue change scrip
that copies the value from one CF to another when the queue
changes.

-Todd

Hello,On Wednesday 07 September 2005 20:06, Todd Chapman wrote:

On Wed, Sep 07, 2005 at 04:51:47PM +0200, Andreas Putzo wrote:

is there a way to prevent users from changing a CustomField depending
on the queue?
I have a CF, which should be editable in queue A.
During the process, the ticket changes its queue to queue B.
There, the CF should only be visible, but NOT editable.

If so, the easiest way might be to create two custom fields with
the same name, and apply one to queue A (read/write) and the
other to queue B (read only). Then write a queue change scrip
that copies the value from one CF to another when the queue
changes.

-Todd

Somehow i discarded the possibility to create a seperate CF
in the second queue too fast.
Of course, this is the best solution, because then i can assign
individual rights to both CustomFields. It’s quite possible, that
eventually some users should be able to customize the CF in
both queues.

Thanks for your hint.

Regards,

Andreas