I have some de-normalized views (for SQL reporting EXTERNAL to RT -
Oracle) and a conversion program for converting Legacy ticket dat into
RT that I want to add to the wiki. I’m not aquainted AT ALL with how to
do this on the RT wiki. I went to “Request Tracker — Best Practical Solutions” and clicked
the “wiki” option. Then I read the instructions to “UpdateTheWiki” and
rapidly got confused (not very hard for me). I now crap about chanig a
website or web page, etc. For example, the term “add
CamelCaseNameOfNewPage to the text of the page and click save” means
absolutely nothing to me. I have no idea what a CamelCaseNameOfNewPage
refers to or how to get my information into whatever that could be.
So, I need a little help here so I can get this info onto the RT wiki.
The views are especially helpfor for those who want to include comments
or ticket history in a SQL report.
Anyway. If anyone is VERY patient and would like to help me out, please
reply. Thanks.
I have some de-normalized views (for SQL reporting EXTERNAL to RT -
Oracle) and a conversion program for converting Legacy ticket dat into
RT that I want to add to the wiki. I’m not aquainted AT ALL with how to
do this on the RT wiki. I went to “Request Tracker... So much more than a help desk — Best Practical Solutions” and clicked
the “wiki” option. Then I read the instructions to “UpdateTheWiki” and
rapidly got confused (not very hard for me). I now crap about chanig a
website or web page, etc. For example, the term “add
CamelCaseNameOfNewPage to the text of the page and click save” means
absolutely nothing to me. I have no idea what a CamelCaseNameOfNewPage
refers to or how to get my information into whatever that could be.
So, I need a little help here so I can get this info onto the RT wiki.
The views are especially helpfor for those who want to include comments
or ticket history in a SQL report.
Anyway. If anyone is VERY patient and would like to help me out, please
reply. Thanks.
Kenn
LBNL
It will create the new page but there can not be non-word characters.
For example, I used “PostgreSQLFullText” for my page on full-text
index support using PostgreSQL. Maybe something like
“DenormalizedViewsForReporting” would be appropriate for your new
page. Then you just start adding content. I used cut-n-paste.
“Camel Case” means to capitalize each word and leave no spaces or
punctuation in between words. It’s called camel casing because it is a
style heavily used in the “Camel Book”, which is O’Reilly’s book on perl
(which has a picture of a camel on the cover). And as you know, RT and
wifty (the wiki application based on jitfy that is running the RT wiki) are
written in perl.
– ============================
Tom Lahti
BIT Statement LLC
punctuation in between words. It’s called camel casing because it is a
style heavily used in the “Camel Book”, which is O’Reilly’s book on perl
(which has a picture of a camel on the cover). And as you know, RT and
Sometimes, logical deduction fails in the face of idiom… ah well, i
suppose i should get that book anyway!
absolutely nothing to me. I have no idea what a CamelCaseNameOfNewPage
…
It will create the new page but there can not be non-word characters.
For example, I used “PostgreSQLFullText” for my page on full-text
That’s camel case - text convention meaning “turning a phrase or
sentence into one word with no spaces and capitalizing each word.”
Humps in the middle, hence camel. So if you’d want to make a page
about converting legacy data to RT, you might call it
ConvertLegacyToRT or something like that.
As you can see from some of the update history, my method for adding
things to the wiki was to look up the http://wiki.bestpractical.com/view/KwikiFormattingRules listed at the
bottom, then made my edits, saved, looked askance at my formatting
errors, edited it again, saved it again, lather rinse repeat until it
looked right. The only risk i can see is that you show up several
times in a row in the edit history, revealing our lack of wik-fu to
all.
I don’t understand custom fields it seems. I have created two of them,
they only appear as an editable field when directly creating a new
ticket rather than having a new ticket opened via inbound email. If the
user wants to edit the field after ticket creation they seem to have to
click on “custom fields” and get taken to another page then click “save
changes”.
What I wanted was to have the custom field as an option when replying to
an email. That way my technicians can simply click on a drop down and
select which product the email reply is in regards to. Can anyone point
me in the right direction to make this happen?
I don’t understand custom fields it seems. I have created two of them,
they only appear as an editable field when directly creating a new
ticket rather than having a new ticket opened via inbound email. If the
user wants to edit the field after ticket creation they seem to have to
click on “custom fields” and get taken to another page then click “save
changes”.
Check the list archives, wiki, or RT book.
CFs are special, and require ACLs.
A normal email has no way of providing content for a CF.
As you can see from some of the update history, my method for adding
things to the wiki was to look up the
http://wiki.bestpractical.com/view/KwikiFormattingRules listed at the
bottom, then made my edits, saved, looked askance at my formatting
errors, edited it again, saved it again, lather rinse repeat until it
looked right. The only risk i can see is that you show up several
times in a row in the edit history, revealing our lack of wik-fu to
all.
Hi, all.
I used Rob’s method as well when I recently added the RTTutorials
page, not really being too familiar with any wiki conventions. It
worked well for me.
Thanks. I DID get my contributions to the wiki. However, they look like
CRAP! I used cut & Paste and the document text is all over the place. no
line delimiters at all. I want people to be able to read what I
contributed, not go blind (ha!). I’m up for any help in making the stuff
readable.
On Mar 10, 2009, at 4:04 PM 3/10/09, Rob Munsch wrote:
As you can see from some of the update history, my method for adding
things to the wiki was to look up the
http://wiki.bestpractical.com/view/KwikiFormattingRules listed at the
bottom, then made my edits, saved, looked askance at my formatting
errors, edited it again, saved it again, lather rinse repeat until it
looked right. The only risk i can see is that you show up several
times in a row in the edit history, revealing our lack of wik-fu to
all.
Hi, all.
I used Rob’s method as well when I recently added the RTTutorials page,
not really being too familiar with any wiki conventions. It worked well
for me.
Thanks. I DID get my contributions to the wiki. However, they look like
CRAP! I used cut & Paste and the document text is all over the place. no
line delimiters at all. I want people to be able to read what I
contributed, not go blind (ha!). I’m up for any help in making the stuff
readable.
Please read the aforementioned formatting page. I cleaned up recently
and it should be fairly straight-forward (and accurate).
Newlines don’t mean what you think they mean;
they don’t mean nothing, only double-newlines mean anything.
You probably want to indent content as code.
Cambridge Energy Alliance: Save money. Save the planet.