[rt-users] How-to-do? Ticket Custom fields with different pragmatics in Ticket life time

[Todd Chapman]

Dirk,

What you want to do is going to be very difficult. If custom field
permissions checking had some context of the current ticket having it's CF
permissions checked then you could do something clean, but unfortunately no
context is provided.

There are callbacks that allow you to override what mason components are
used to display each CF and they do have ticket/page context, so you could
use them to display edit/display read-only/not display based on the ticket
and what context the CF is being viewed in.

-Todd

On 1/18/08, Dirk Pape <pape-rt at inf.fu-berlin.de> wrote:
>
> Hallo,
>
> --Am 18. Januar 2008 11:22:19 +0100 schrieb Dirk Pape
> <pape-rt at inf.fu-berlin.de>:
>
> > For "pragmatic kind" of cf cannot be stored anywhere an "mandatory"
> > status does not depend on the "pragmatic kind".
>
> this sentence is t a sentence I think, so next try.
>
> cfs for now have only a category (type) but there is no attribute to give
> them the desired "pragmatics", that is on which pages they will be shown
> or
> can be entered and in which stage of the ticket they become mandatory.
>
> I look for a way to express this in the database and use this information
> in the mason code systematically.
>
> Regards, Dirk.
>
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20080118/2a3717cc/attachment.htm>