Ruslan,
> Well, it doesn't explain need to abuse Type and Instance. Above
> description unclear on what is "bookmarked ticket". Last value makes no
> sense - if user commented on 20 tickets within last 24 hours then 15 of
> them are not "bookmarked", so 15 tickets are not bookmarked by this
>
On Mon, Jun 17, 2013 at 6:13 PM, Jean-Christophe Boggio <
rt-us...@thefreecat.org> wrote:
> Ruslan,
>
> Thanks for your comments.
>
>
> I can believe that. Our po files getting big and loading them takes
>> time. I have "loading po files on demand" patch on my todo, but not sure
>> when I get to
BTW, while I'm at it, the "links" table also misses such an 'instance'
field :
When we link assets to tickets, we would like to distinguish between
what we consider the "main" asset and the "related" assets.
Examples :
- "sites" are assets. One ticket is created for a "site" but may concern
Ruslan,
Thanks for your comments.
I can believe that. Our po files getting big and loading them takes
time. I have "loading po files on demand" patch on my todo, but not sure
when I get to it.
No problem for me but sure, it'll be a good improvement.
Note that Type is going away in RT 4.2, s
On Sat, Jun 15, 2013 at 5:04 AM, Jean-Christophe Boggio <
rt-us...@thefreecat.org> wrote:
> Le 14/06/2013 20:58, Kevin Falcone a écrit :
>
> It actually wants an RT::CurrentUser, but RT will do the conversion
>> for you.
>>
>
> Thanks for this info, I'll see if I can do better. Any hint for the n
Le 14/06/2013 20:58, Kevin Falcone a écrit :
It actually wants an RT::CurrentUser, but RT will do the conversion
for you.
Thanks for this info, I'll see if I can do better. Any hint for the
new() methods ? Where are they declared ?
As a side note, the RT->Init() is very long, mainly because
On Tue, Jun 11, 2013 at 11:24:54AM +0200, Jean-Christophe Boggio wrote:
> # As I understand it, RT's $TicketObj->new expects a RT::User parameter
> # which will be the "CurrentUser"
It actually wants an RT::CurrentUser, but RT will do the conversion
for you.
>
> As a side note, the RT->Init() is
Ok, I did it and it seems to work like I want it to. There are still
things that I don't understand but they might be related to my lack of
Perl knowledge, for example : why can't I find the declaration for
RT::User->new or RT::Ticket->new ?
For the record I did this :
use lib qw(/usr/share/
Le 07/06/2013 18:36, Kevin Falcone a écrit :
While the REST interface (which is what the command line client uses)
does not allow you to impersonate a user without knowing passwords or
cookies, you can use RT's core perl API to load any user and record
actions as that user.
Thanks for your answ
On Fri, Jun 07, 2013 at 01:04:38AM +0200, Jean-Christophe Boggio wrote:
> Thanks for your answers but that's not what I'm looking for. This
> method will work if I store the passwords for every user in clear
> form.
>
> What I want is to only have the root (admin) passwd in a RT Config
> File and
Thanks for your answers but that's not what I'm looking for. This method
will work if I store the passwords for every user in clear form.
What I want is to only have the root (admin) passwd in a RT Config File
and issue the comment/correpond AS some user. I am making a dedicated
interface to R
With env variable
RTUSER=john
Optional:
RTPASSWD=johnubberpassword@
-Mensagem original-
De: rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] Em nome de Jean-Christophe
Boggio
Enviada em: quinta-feira, 6 de junho de 2013 13:31
Para: RT Users
Ass
12 matches
Mail list logo
