hello rt users,
as i more and more rely on mutt+vim+commandByMail, i would like
omnicompletion to complete the names of queues, status and categories
when i fill the ticket.
the only way i saw to get those list remotely is to scrap the
queryBuilder (/rt/Search/Build.html) which isn't that
On Mon, Mar 10, 2014 at 03:13:26PM -0430, Daniel Soto wrote:
Hello, i am having issues with the Assets extension.
I am using Debian 7.3, with request tracker 4.2.3 built from source.
I am also using the external auth extension, so i can use our Active
Directory database for
Unfortunettly it's not working.
What I understood is this "RequestorGroup.Name = 'foo' " should be
added in Search/Edit.html?NewQuery=1 (Advenced on Query Builder)
I tried Queue=foo and RequestorGroup.Name="MO Mechanicy Strefa"
0 tickets found
Ok, as a workaround this works
RequestorGroup.Id = 105 AND Queue != 'MO.Mechanicy.Strefa'
(id 105 is group MO Mechanicy Strefa which maitain tickets in Queue
MO.Mechanicy.Strefa)
Thanx.
W dniu 2014-03-11 12:36, Bartosz Maciejewski pisze:
Unfortunettly it's not working.
What I understood
1) The asset number is also displayed just below the RT menu.
2) I see this requiring a code extension to have the query run against
both tables as it currently runs against ticket titles and not articles or
assets.
Keith
From: rt-users-boun...@lists.bestpractical.com
Hello All
Has anyone built a list of comments that can be selected for a ticket when
closing the ticket?
Meaning when setting the ticket to Resolved and you are on the edit screen have
a list of canned response to select from to be pasted into the comment section.
Thanks
Bryon Baker
Network
On Tue, Mar 11, 2014 at 02:43:22PM +, Bryon Baker wrote:
Hello All
Has anyone built a list of comments that can be selected for a ticket when
closing the ticket?
Meaning when setting the ticket to Resolved and you are on the edit screen
have a list of
And one last follow-up about this: here are my import statistics. The
importer used up to about 800MB of RAM, so better than the serializer,
but still pretty high. Also, 108 hours seems like a long time to
import records that took only 4 hours to export, and this is on a
pretty high-end MySQL
