This is definitely a plugin that I would use... a *lot*.
On Fri, Sep 9, 2016 at 11:29 AM, Alex Hall wrote:
> As long as I know it's not built in and buried in settings somewhere, I
> won't pursue it. I'll wait until things are working and I'm more
> comfortable before trying
I agree that this would be a wonderful extension. I use markdown a lot with
other web-based apps.
Keith Creasy, Programmer and Technical Lead
American Printing House f/t Blind
Phone: 502.895.2405
Skype: keith537
From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of
Hello all,
The other major problem my boss has with RT is how emailed replies include
quoted text/original messages. If four replies come in, each carrying with
it the entire conversation history, the web UI showing the ticket very
quickly becomes a huge mess. I found a thread from this list that
I'm not even installing from source, just the pre-built package (4.2.8) for
Debian. When I issue the command, I get a lot of
depends: libcss-squish-perl but it is no installable
depends: libstring-shellquote-perl but it is not installabl
depends: libcrypt-xi09-perl but it is not installable
and
I would personally avoid editing the database manually. Instead I would simply
stop new mail from coming in from users/staff and disable the Scrip that would
send the notification until the import is done.
On Sep 12, 2016, at 9:08 AM, Tim Gustafson wrote:
>
> We just finished
On Sep 12, 2016, at 12:39 PM, Alex Hall
> wrote:
When I issue the command you suggested:
Can't open perl script: no such file or directory
Something seems very off about the Perl installation on this server, given that
all the dependencies it can't
Hey all,
Our virtual server host isn't too familiar with Linux. We have a Debian
server, finally, but when I try to apt-get install request-tracker4, I get
a bunch of errors about not being able to install dependencies. I'm using
the sources the original install came with. What source(s) do I need
I would not use the repo version even without familiarity with Linux - it would
make things actually more difficult later. I would follow the instructions
exactly as they are written by BestPractical from the .tar.gz on their site.
One thing you can do to make life a little easier before
> On Sep 12, 2016, at 12:32 PM, Landon Stewart wrote:
>
> I would not use the repo version even without familiarity with Linux - it
> would make things actually more difficult later. I would follow the
> instructions exactly as they are written by BestPractical from
Thanks, I'll give that a try although the shell command on my server is giving
a different error. Will post output once I have ssh access.
I have tried reinstalling 4.2.10 and fresh installing 4.4.1 with no change in
behaviour. Fixdeps run in both cases. Also, debug log (rt.log) works for
On Mon, Sep 12, 2016 at 09:08:44AM -0700, Tim Gustafson wrote:
> We just finished importing around 50,000 tickets from one RT instance
> into another instance with its own large collection of tickets. The
> rt-importer script put them into new queues (which we expected) rather
> than the ones we
We just finished importing around 50,000 tickets from one RT instance
into another instance with its own large collection of tickets. The
rt-importer script put them into new queues (which we expected) rather
than the ones we had already created in the destination system for the
cut-over. I went
On Mon, Sep 12, 2016 at 12:53:37PM -0400, Alex Hall wrote:
> Hi all,
> My boss has just been looking through RT, and he didn't like that everyone
> in a queue was emailed for every ticket. I've removed queue staff and admin
> groups as watchers so this won't happen again, and we'll rely on
I had to install a bunch of perl modules after the upgrade. (Probably
"make fixdeps" or reinstalling RT would have done the same, more
quickly, but I'm kind of stubborn sometimes. Also this wasn't our
production server so I had some freedom to just poke at it and figure
out what it needed.)
>> update Tickets set queue = 1234 where queue = 4321
> That is how I have done it to avoid the notification flurry.
Thanks, I'm going to go with that for now. :)
--
Tim Gustafson
t...@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A
-
RT 4.4 and RTIR training sessions, and a new
Great news! After adding httpredir.debian.org/debian to my sources list,
then running apt-get update, then running apt-get install request-tracker4
--fix-missing, installation appears to be proceeding! I'll email if
something goes disasterously wrong, but we're looking good for the moment.
Thanks!
This is the error that I am getting on the command line. If anyone has any
insights, I would be most grateful before I dive into the switch to mod_fcgid
with apache2 tonight:
# /opt/rt4/sbin/rt-server.fcgi -processes 5 -idle-timeout 300
STDIN is not a socket, and no --listen, --socket, or
Hi all,
My boss has just been looking through RT, and he didn't like that everyone
in a queue was emailed for every ticket. I've removed queue staff and admin
groups as watchers so this won't happen again, and we'll rely on entering
users into the one-time CC and Admin CC boxes instead, not to
To my very inexperienced eye, nothing stands out between the two servers. I
also had a look at sources.list for both, and the only difference I see is
in the mirrors. One has no mirrors selected, but it does have the basic
security.debian.org sources; the other has some mirrors for Digital Ocean,
On Sep 12, 2016, at 2:51 PM, Pavneet Arora
> wrote:
This is the error that I am getting on the command line. If anyone has any
insights, I would be most grateful before I dive into the switch to mod_fcgid
with apache2 tonight:
#
Apache2 config unchanged from before the upgrade to 16.04.1 (host name and
alias obscured):
# Tell FastCGI to put its temporary files somewhere sane; this may
# be necessary if your distribution doesn't already set it
#FastCgiIpcDir /tmp
FastCgiServer /opt/rt4/sbin/rt-server.fcgi -processes 5
Hi,
We just moved a bunch of users to an RT instance that uses LDAP
authentication, as opposed to RT-specific passwords. Some of our
users don't read our announcement e-mails (imagine that...) and are
trying to log in using their old RT-specific password, which is
causing them to send e-mails
22 matches
Mail list logo