Bug#184406: marked as done (RFP: rtfm -- Request Tracker FAQ Manager)
Your message dated Mon, 10 Nov 2003 18:03:49 -0500
with message-id <E1AJL4X-0006G4-00@auric.debian.org>
and subject line Bug#184406: fixed in rtfm 2.0.1-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 12 Mar 2003 02:58:52 +0000
>From samj@aos.net.au Tue Mar 11 20:58:52 2003
Return-path: <samj@aos.net.au>
Received: from (retina.ranzco.edu) [61.95.31.50]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 18swSB-0005Pd-00; Tue, 11 Mar 2003 20:58:51 -0600
Received: (qmail 12442 invoked from network); 12 Mar 2003 02:58:49 -0000
Received: from unknown (HELO aos.net.au) (10.2.32.212)
by 61.95.31.50 with SMTP; 12 Mar 2003 02:58:49 -0000
Message-ID: <3E6EA337.50608@aos.net.au>
Date: Wed, 12 Mar 2003 14:02:15 +1100
From: Sam Johnston <samj@aos.net.au>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: submit@bugs.debian.org
CC: tfheen@debian.org
Subject: RFP: rtfm -- Request Tracker FAQ Manager
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-1.5 required=4.0
tests=HAS_PACKAGE,SPAM_PHRASE_02_03,USER_AGENT,
USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG
version=2.44
X-Spam-Level:
Package: wnpp
Version: N/Ap reported 2003-03-12
Severity: wishlist
RTFM (The RT FAQ Manager) is a tool for maintaining an organizational
knowledgebase. Out of the box, it integrates with RT3 (Also available from
bestpractical.com).
Installation instructions:
0) Download from
http://bestpractical.com/pub/rt/devel/rtfm-2-0-beta-1.tar.gz
1) Install RT 3.0.x [or 2.1.8x for the moment ]
2) Once RT 3.0 appears to be happily installed, cd into the directory you
unpacked RTFM into.
3) Edit RTFM's Makefile to point to your RT 3 instance
4) make sure that mysql or pgsql's commandline tool is in your path
5) Type "make install"
6) stop and start your web server
Staff users should be now have a new "RTFM" menu item RT's top level menu.
As an administrator, you should go create some "Classes" of articles in
RTFM.
Classes are equivalent to RT's queues. Unlike RTFM 1.0, RTFM 2.0 doesn't
have a
single "body" section for each article. Everything is a custom field (except
for name, summary and some other basic metadata). So, you need to go create
some custom fields. You've got five choices. "SelectSingle" and
"SelectMultiple" let you pick one or many choices from a list respectively.
"FreeformSingle" and "FreeformMultiple" let you hand-enter one or many
lines of
text. "TextSingle" is what you want for the "Body" of articles. Once you've
created your custom fields, go into your classes and click on "Custom
Fields"
and add the Custom Fields you want to each class.
Grant some ACLs to your users and start creating articles.
Of course, RTFM integrates with RT. You can extract the body of a
ticket into
an article. Within RT, you should now see an "Extract to article" button in
the upper right hand corner of RT's UI when working with tickets. When you
click that button, RTFM will ask you which Class to create your new
article in.
Once you click on a class name, the Ticket's transactions will be displayed,
along with a set of select boxes. For each transaction, you can pick which
TextSingle that transaction should be extracted to. From there on in,
it's just
regular article creation. And the integration doesn't stop there! When
replying to or commenting on tickets, there's a new UI widget that lets you
search for and include RTFM articles in your reply. (They're editable, of
course).
Development of RTFM 2.0 has been sponsored by RIPE NCC and DynDNS.org
You probably want to discuss rtfm on rt-devel@lists.fsck.com at this point.
(Send mail to rt-devel-request@lists.fsck.com to subscribe)
Best,
Jesse Vincent
Best Practical Solutions, LLC
-- http://www.bestpractical.com/rt -- Trouble Ticketing. Free.
---------------------------------------
Received: (at 184406-close) by bugs.debian.org; 10 Nov 2003 23:08:28 +0000
>From dsilvers@auric.debian.org Mon Nov 10 17:08:23 2003
Return-path: <dsilvers@auric.debian.org>
Received: from auric.debian.org [206.246.226.45]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AJL8v-0001er-00; Mon, 10 Nov 2003 17:08:21 -0600
Received: from dsilvers by auric.debian.org with local (Exim 3.35 1 (Debian))
id 1AJL4X-0006G4-00; Mon, 10 Nov 2003 18:03:49 -0500
From: Sam Johnston <samj@aos.net.au>
To: 184406-close@bugs.debian.org
X-Katie: lisa $Revision: 1.25 $
Subject: Bug#184406: fixed in rtfm 2.0.1-1
Message-Id: <E1AJL4X-0006G4-00@auric.debian.org>
Sender: Daniel Silverstone <dsilvers@auric.debian.org>
Date: Mon, 10 Nov 2003 18:03:49 -0500
Delivered-To: 184406-close@bugs.debian.org
Source: rtfm
Source-Version: 2.0.1-1
We believe that the bug you reported is fixed in the latest version of
rtfm, which is due to be installed in the Debian FTP archive:
rtfm_2.0.1-1.diff.gz
to pool/main/r/rtfm/rtfm_2.0.1-1.diff.gz
rtfm_2.0.1-1.dsc
to pool/main/r/rtfm/rtfm_2.0.1-1.dsc
rtfm_2.0.1-1_all.deb
to pool/main/r/rtfm/rtfm_2.0.1-1_all.deb
rtfm_2.0.1.orig.tar.gz
to pool/main/r/rtfm/rtfm_2.0.1.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 184406@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sam Johnston <samj@aos.net.au> (supplier of updated rtfm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 7 Nov 2003 10:02:23 +1100
Source: rtfm
Binary: rtfm
Architecture: source all
Version: 2.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Sam Johnston <samj@aos.net.au>
Changed-By: Sam Johnston <samj@aos.net.au>
Description:
rtfm - RT FAQ Manager
Closes: 184406
Changes:
rtfm (2.0.1-1) unstable; urgency=low
.
* Initial Release. Closes: #184406.
Files:
e8fe32136f53a6001e4212884f8244ee 547 misc optional rtfm_2.0.1-1.dsc
955a5f0f240252b8c97deb8074445fa3 80905 misc optional rtfm_2.0.1.orig.tar.gz
15c953760dc9681533a8296a529c4759 3668 misc optional rtfm_2.0.1-1.diff.gz
281f1bf2b12f29eb6f5d86f03e815bbb 69224 misc optional rtfm_2.0.1-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/qvXhj4XJViLpTR0RAsv1AJ9/uCw3semJLd7f4mETBtXP2NtT2ACfXeYN
nCz/47TTIc7Pv6sUwKSm7kA=
=PgGI
-----END PGP SIGNATURE-----
Reply to: