Re: [lopsa-tech] issue tracking

2013-03-17 Thread Starchy
On 3/17/13 5:30 PM, Derek Balling wrote: > > On Mar 17, 2013, at 8:24 PM, Starchy wrote: >> My only major complaint with the system is that when a user emails in to >> create a ticket for the first time, it automatically creates an account >> for them, and emails them an account creation email wi

Re: [lopsa-tech] issue tracking

2013-03-17 Thread Derek Balling
On Mar 17, 2013, at 8:24 PM, Starchy wrote: > My only major complaint with the system is that when a user emails in to > create a ticket for the first time, it automatically creates an account > for them, and emails them an account creation email with credentials in > plaintext. This is both inse

Re: [lopsa-tech] issue tracking

2013-03-17 Thread Starchy
On 3/13/13 9:51 AM, Derek Balling wrote: > > On Mar 13, 2013, at 12:35 PM, Frank Thommen wrote: >> Clearly OTRS (http://www.otrs.com/en/). After having gone through the >> manual RT installation hell twice, installing OTRS (on CentOS) was just >> nothing. It's quite different from RT, but I'm

Re: [lopsa-tech] issue tracking

2013-03-13 Thread Derek Balling
On Mar 13, 2013, at 12:35 PM, Frank Thommen wrote: > Clearly OTRS (http://www.otrs.com/en/). After having gone through the manual > RT installation hell twice, installing OTRS (on CentOS) was just nothing. > It's quite different from RT, but I'm absolutely happy with it (caveat: I'm > only u

Re: [lopsa-tech] issue tracking

2013-03-13 Thread Frank Thommen
On 11.03.13 19:51, Edward Ned Harvey (lopser) wrote: [...] My question is: What ticketing systems would you recommend as alternatives to RT? Clearly OTRS (http://www.otrs.com/en/). After having gone through the manual RT installation hell twice, installing OTRS (on CentOS) was just nothing

Re: [lopsa-tech] issue tracking

2013-03-12 Thread Scott Roberts
ay, March 11, 2013 2:51 PM To: LOPSA Technical Discussions mailto:t...@lopsa.org>> Subject: [lopsa-tech] issue tracking As an IT person, I deal with tech support from a lot of different companies. Whenever *they* do a good job, I notice, they're usually running on RT. (A good job in ter

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Alexios Zavras
Edward Ned Harvey (lopser) wrote [edited]: > I am sitting here now, realizing that RT is written in perl CGI, > and I'm having a *really* hard time convincing myself > that Perl CPAN hell is the right way to go. Since I was doing exactly the same thing this morning, I can offer my setup: - set up

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Stephan Fabel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As an alternative, consider asking Best Practical to install it for you. They do so for a very reasonable price. We've just gone through this and works like a charm. - -Stephan On 03/11/2013 09:05 AM, Atom Powers wrote: > As somebody who happily u

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Dan Ritter
On Mon, Mar 11, 2013 at 07:11:20PM +, Edward Ned Harvey (lopser) wrote: > > From: Dan Ritter [mailto:d...@randomstring.org] > > > > Build a Debian Wheezy virtual machine. Run the Debian-supplied > > RT package in that. Run apticron so you will get reminders as to > > when packages have updated

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Christopher Webber
It is a little rough around the edges but this is a puppet module that I wrote at $lastjob that used to work: https://github.com/cwebberOps/rt-vagrant/tree/master/modules/rt -- cwebber On Mar 11, 2013, at 12:00 PM, Dan Ritter wrote: > On Mon, Mar 11, 2013 at 06:51:07PM +, Edward Ned Harve

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Edward Ned Harvey (lopser)
> From: Dan Ritter [mailto:d...@randomstring.org] > > Build a Debian Wheezy virtual machine. Run the Debian-supplied > RT package in that. Run apticron so you will get reminders as to > when packages have updated. If it's better than the centos solution, I'll happily go with it ... Here has been

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Brandon Allbery
On Mon, Mar 11, 2013 at 2:51 PM, Edward Ned Harvey (lopser) < lop...@nedharvey.com> wrote: > I used this experience to guide me, in choosing a ticketing system to > deploy and satisfy the need at a client company. (In progress.) Their > internal support staff need something to keep track of iss

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Dan Ritter
On Mon, Mar 11, 2013 at 06:51:07PM +, Edward Ned Harvey (lopser) wrote: > As an IT person, I deal with tech support from a lot of different companies. > Whenever *they* do a good job, I notice, they're usually running on RT. (A > good job in terms of managing a ticket, responding timely, no

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Atom Powers
As somebody who happily used RT for many years, I am quite impressed with OTRS which I now use. (Part of my reason for changing was that I corrupted my RT install trying to upgrade.) I don't think OTRS will behave any more easily with selinux though. On Mon, Mar 11, 2013 at 11:51 AM, Edward Ned

Re: [lopsa-tech] issue tracking

2013-03-11 Thread Tom Limoncelli
Your compliments about RT reflect that the author(s) made a key realization early on: Request tracking is a communication tool for working with customers. This is very different that if you are building, for example, a bug tracking system. The CPAN hell issue can be avoided. For example Debian h

[lopsa-tech] issue tracking

2013-03-11 Thread Edward Ned Harvey (lopser)
As an IT person, I deal with tech support from a lot of different companies. Whenever *they* do a good job, I notice, they're usually running on RT. (A good job in terms of managing a ticket, responding timely, not premature closing tickets or forgetting about them, etc.) I start a support re