Nope, not there. I have
Status: field Owner: field Worked: fieldfield
Update Type: field
Subject: field
Cc: field
Bcc: field
Attach: fieldbuttonbutton
Message: field
Keep up with me and what I'm up to: http://theillien.blogspot.com
Raed El-Hames wrote:
It should already be there -the row
Also, as the admin I have SuperUser rights so permissions shouldn't be the
issue.
Keep up with me and what I'm up to: http://theillien.blogspot.com
Raed El-Hames wrote:
It should already be there -the row between Status and update type .. or
am I mis-understanding your question
I am
Sorry Mathew you are absolutely right, I so used to my customised
version that I forgot what is out of the box, I am not sure why the RT
folks left it out.
You can add the queue either using call backs (though not sure how to do
this - If you get a working call back please tell me how these are
Callbacks confuse me. I wish they were easier to manage and make sense of.
I'll try your approach. Thanks.
Keep up with me and what I'm up to: http://theillien.blogspot.com
Roy El-Hames wrote:
Sorry Mathew you are absolutely right, I so used to my customised
version that I forgot what is
I've followed the method laid out in the wiki for automated approvals in order
to create child tickets.
I've created the following template:
===Create-Ticket: Child
Subject: {$Tickets{'TOP'}-Subject} - Child
Depended-on-by: TOP
Status: new
Queue: TechOps
Type: ticket
Refers-To:
That wouldn't be it. I set custom fields in other scrips.
Keep up with me and what I'm up to: http://theillien.blogspot.com
Drew Barnes wrote:
IIRC, Custom fields are set in a different transaction than the ticket
creation. Perhaps this is tripping you up?
Mathew Snyder wrote:
Mathew
Mathew Snyder wrote:
I've followed the method laid out in the wiki for automated approvals in order
to create child tickets.
I've created the following template:
===Create-Ticket: Child
Subject: {$Tickets{'TOP'}-Subject} - Child
Depended-on-by: TOP
Status: new
Queue: TechOps
Type:
IIRC, Custom fields are set in a different transaction than the ticket
creation. Perhaps this is tripping you up?
Mathew Snyder wrote:
Mathew Snyder wrote:
I've followed the method laid out in the wiki for automated approvals in
order
to create child tickets.
I've created the
Ah. I think I see it here:
I've created the following template:
===Create-Ticket: Child
Subject: {$Tickets{'TOP'}-Subject} - Child
Depended-on-by: TOP
Status: new
Queue: TechOps
Type: ticket
Refers-To: {$Tickets{'TOP'}-Id()}
Content: This is a child ticket
ENDOFCONTENT
And a scrip which makes
Hi,
i'm starting to use rt 3.6 from a little time .. someone
have made a scrip that unzip ad upload files from attachments?
thanks in advance for your helps
Marco
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help:
Chet Burgess wrote:
Greetings,
I had a user report a problem with categories in custom fields recently
that I have been unable to solve. I have looked through the wiki, the
bugs listed in rt, and the mailing lists and I have been unable to find
a solution to my problem.
We have
Hi,
Im Portuguese, and my users and I send emails in Portuguese, but when RT
sends my comments, the Portuguese characters such as the ç the à, á, ó and
others, dont appear, instead I get some codes.
I believe this is due to the character set. How do I change it?
Thanks,
CS
For a RT installation (3.6.4 upgraded from 3.6.3), I have the
following situation for a group throught the admin interface:
I can see some users on the left side, but I cannot remove them
(checking the checkbox). RT returns: 'Group has no such member', and
the user stays on the left side...
If I
SOLVED.
Oops, by accident a group became a subgroup of another one. I should
have scrolled down the page to see that.
This explains the entry in the CacheGroupMembers table.
The UI could be made more intuitive: checkboxes should not be
displayed for users inherited from subgroups. Or these
14 matches
Mail list logo
