From: "Dahmen Stephen" <dahmens@bah.com>
To: gnats-devel@sourceware.cygnus.com
Subject: Re: GNATS Usage
Date: Fri, 30 Apr 1999 07:38:00 -0000 [thread overview]
Message-ID: <3.0.5.32.19990430093726.00b1bbb0@mclean2-mail.usae.bah.com> (raw)
In-Reply-To: <Pine.GSO.4.10.9904292104520.16954-100000@sys4>
At 09:06 PM 4/29/99 -0600, Rick Macdonald wrote:
>On Thu, 29 Apr 1999, Jeff Johnson wrote:
>
>> I'm looking to implemnt more of a customer issue-tracking system,
>> rather than a bug tracking system, that can be used completely
>> through a web interface (with email integration) and I was wondering
>> if GNATS was the right choice. Are there any other ticket/issue
>> tracking systems available for tracking customer service and/or
>> local software issues that are freely available with or without
>> source? What about Debians bug-tracking system?
>
>The latest gnats-beta-3.110 fits this. The new gnatsweb is the thing for
>you to look at.
I would agree. I'm in the midst of pitching GNATS to my management to
handle just this very thing. Actuall, we'll be using it as not only a
customer tracking base, but also to track our own internal knowledge of
various system failures. Thus, when some fault occurs in our system, a
developer can search the GNATS base and find relevant issues from the past
that may relate.
The one thing it lacks is a web interface to manipulate the
configuration... all that is done via vi on the Unix side. Which is a
bummer, because in some situations you might want someone to administer
this tool who is not UNIX friendly. Perhaps in the future.
Regards,
STephen
next prev parent reply other threads:[~1999-04-30 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-29 15:21 Jeff Johnson
1999-04-29 21:00 ` Rick Macdonald
1999-04-30 7:38 ` Dahmen Stephen [this message]
1999-04-30 7:38 ` Rick Macdonald
1999-04-30 7:38 ` Jeff Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.5.32.19990430093726.00b1bbb0@mclean2-mail.usae.bah.com \
--to=dahmens@bah.com \
--cc=gnats-devel@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).