Time Worked Report

Walid,

Also, we used to have a different $home than /opt/rt3/ (in Solaris) and it
caused endless problems when trying to implement extensions. We decided to
just go to opt/rt3 and put it in VM and we’ve been sailing smoothly ever
since. Just a thought for you to consider.

Kenn
LBNLOn Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Walid,

Well, Wherever you have the …/Tools/Report/… you will need a
…/local/Tools/Report/ version to put “TimeWorkedReport”.

Kenn
LBNL

On Tue, Mar 29, 2011 at 7:00 AM, Walid Haider walid.haider@movensis.comwrote:

Hi Johan,

No, I do not. Should I go ahead and create it and then follow Kenn’s
instructions?

Regards,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Johan Sjöberg
Sent: terça-feira, 29 de Março de 2011 14:56

To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Do you have a /usr/local/rt3?

/Johan

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Walid Haider
Sent: den 29 mars 2011 15:20
To: Kenneth Crocker; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Kenn,

Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my
$home is /usr/share/rt3. My folder structure is different compared to what
you mention below, as I do not have a share directory within my RT $home.

Please advise if I should create the local directory within
/usr/share/rt3.

Thanks,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: segunda-feira, 28 de Março de 2011 17:33
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Walid,

What I mean is this; it is highly recommended that any changes you make
to RT code be done in a “local” version. RT will automatically look to
$Home/local/…/…/ (where $home is usually opt/rt3/) for any
override code
that an installation may have developed. In this example
(TimeWorkedReport), I copied the various /$home*/share/…/…
directories & files listed in the "readme’ for that report into a /$home/
local/…/… version/copy of those directoryies & files. I did *
NOT
make any changes to any /share/ version of RT code. This is
recommended for a couple reasons; the least of which it is easier to
maintain later versions
of RT without wiping out your local code
(provided you keep a copy of that code). Also, industry wide for about the
last 40 years, it has been considered a best practice to never mess
with original code, but to provide a method that allows you to use other
code instead.

So, my advice is to first; return all /share/ code to it’s original state.
Then create $home*/local/*html/Tools/Reports directories in order to
copy/create the files mentioned in the “TimeWorkedReport” documentation.
That’s what I did:

  1. If it exists,type “/opt/rt3/local/html/Elements/” otherwise,
    create it.
  2. Copy the “delivered” file (from …/share/…) SelectQueue over to
    this directory with a the new name.
    A) Type “cp /opt/rt3/share/html/Elements/SelectQueue
    SelectMultiQueue”
    .
  3. Replace the code in “SelectMultiQueue” with the code specified for
    this file from the document the “TimeWorkedReport".
  4. If it exists, type “/opt/rt3/local/html/Tools/” , otherwise,
    create it.
  5. Create new directories:
    A) Create “Reports” directory within *“Tools”
    *B) Get into “Reports” directory.
    C) Create “Elements” directory within “Tools/Reports”
  6. Copy the “delivered” files (from …/share/…) (Tabs, index.html)
    over to the new directories:
    A) Copy the “Tabs” file over to “Tools/Reports/Elements”:
    1) Within “Elements”, type “cp
    /opt/rt3/share/html/Tools/Reports/Elements/Tabs .”
    .
    2) Go back 1 directory level to get to “/Tools/Reports”.
    3) Copy the “index.html” file over to “Tools/Reports” twice:
    a) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html .”
    .
    b) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html TimeWorkedReport.html”
    .
  7. Modify/Replace the code in *“Tabs”, “index.html” & “TimeWorkedReport”
    *with the code specified for these files from the document the “Time
    Worked Report”
    .

Anyway, This is the procedure I followed and I had absolutely no problems
AND I didn’t have to worry about Production being messed up.

Also, I’m in 3.8.7 so I made sure to follow the 3.8 instructions.

Hope this helps.

Kenn
LBNL

Opps, that was supposed to be /local/html/Tools/Report. Sorry.

KennOn Tue, Mar 29, 2011 at 8:39 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Walid,

Also, we used to have a different $home than /opt/rt3/ (in Solaris) and it
caused endless problems when trying to implement extensions. We decided
to just go to opt/rt3 and put it in VM and we’ve been sailing smoothly ever
since. Just a thought for you to consider.

Kenn
LBNL

On Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker kfcrocker@lbl.govwrote:

Walid,

Well, Wherever you have the …/Tools/Report/… you will need a
…/local/Tools/Report/ version to put “TimeWorkedReport”.

Kenn
LBNL

On Tue, Mar 29, 2011 at 7:00 AM, Walid Haider walid.haider@movensis.comwrote:

Hi Johan,

No, I do not. Should I go ahead and create it and then follow Kenn’s
instructions?

Regards,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Johan Sjöberg
Sent: terça-feira, 29 de Março de 2011 14:56

To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Do you have a /usr/local/rt3?

/Johan

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Walid Haider
Sent: den 29 mars 2011 15:20
To: Kenneth Crocker; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Kenn,

Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my
$home is /usr/share/rt3. My folder structure is different compared to what
you mention below, as I do not have a share directory within my RT $home.

Please advise if I should create the local directory within
/usr/share/rt3.

Thanks,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: segunda-feira, 28 de Março de 2011 17:33
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Walid,

What I mean is this; it is highly recommended that any changes you
make to RT code be done in a “local” version. RT will automatically
look to $Home/local/…/…/ (where $home is usually opt/rt3/) for any
override code
that an installation may have developed. In this example
(TimeWorkedReport), I copied the various /$home*/share/…/…
directories & files listed in the "readme’ for that report into a /$home/
local/…/… version/copy of those directoryies & files. I did *
NOT
make any changes to any /share/ version of RT code. This is
recommended for a couple reasons; the least of which it is easier to
maintain later versions
of RT without wiping out your local code
(provided you keep a copy of that code). Also, industry wide for about the
last 40 years, it has been considered a best practice to never mess
with original code, but to provide a method that allows you to use other
code instead.

So, my advice is to first; return all /share/ code to it’s original
state. Then create $home*/local/*html/Tools/Reports directories in order
to copy/create the files mentioned in the “TimeWorkedReport” documentation.
That’s what I did:

  1. If it exists,type *“/opt/rt3/local/html/Elements/” *otherwise, create it.
  2. Copy the “delivered” file (from …/share/…) SelectQueue over
    to this directory with a the new name.
    A) Type “cp /opt/rt3/share/html/Elements/SelectQueue
    SelectMultiQueue”
    .
  3. Replace the code in “SelectMultiQueue” with the code specified for
    this file from the document the “TimeWorkedReport".
  4. If it exists, type “/opt/rt3/local/html/Tools/” , otherwise,
    create it.
  5. Create new directories:
    A) Create “Reports” directory within *“Tools”
    *B) Get into “Reports” directory.
    C) Create “Elements” directory within “Tools/Reports”
  6. Copy the “delivered” files (from …/share/…) (Tabs, index.html)
    over to the new directories:
    A) Copy the “Tabs” file over to “Tools/Reports/Elements”:
    1) Within “Elements”, type “cp
    /opt/rt3/share/html/Tools/Reports/Elements/Tabs .”
    .
    2) Go back 1 directory level to get to “/Tools/Reports”.
    3) Copy the “index.html” file over to “Tools/Reports” twice:
    a) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html .”
    .
    b) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html TimeWorkedReport.html”
    .
  7. Modify/Replace the code in *“Tabs”, “index.html” &
    “TimeWorkedReport” *with the code specified for these files from the
    document the “Time Worked Report”.

Anyway, This is the procedure I followed and I had absolutely no problems
AND I didn’t have to worry about Production being messed up.

Also, I’m in 3.8.7 so I made sure to follow the 3.8 instructions.

Hope this helps.

Kenn
LBNL

Hi Kenn,

Thanks for the tip regarding RT $home, I will definitely consider it.

I must be missing something, as I cannot see the Time Worked Report option on the menu.

This is what I did:

  1.   Created a local directory within /usr/share/rt3, and then created the /usr/share/rt3/local/html and /usr/share/rt3/local/html/Elements directories.
    
  2.   Created the new file SelectMultiQueue (with the relevant content) within /usr/share/rt3/local/html/Elements
    
  3.   Created .../rt3/local/Tools, .../rt3/local/Tools/Reports, and .../rt3/local/Tools/Reports/Elements directories
    
  4.   Copied the Tabs file from /usr/share/rt3/html/Tools/Reports/Elements/Tabs to .../rt3/local/Tools/Reports/Elements
    
  5.   Copied the index.html file from /usr/share/rt3/html/Tools/Reports/index.html to .../rt3/local/Tools/ and edited the file accordingly
    
  6.   Created the TimeWorkedReport.html  (with the relevant content) file in .../rt3/local/Tools/
    
  7.   I restarted httpd and logged into RT, but could not see  the Timed Worked Report option on the menu
    

I then tried moving the index.html and TimeWorkedReport.html files from /usr/share/rt3/local/html/Tools/Reports into /usr/share/rt3/local/html/Tools/. But after restarting httpd, I still could not see the Time Worked Report.

Finally, I tried creating the local directory in /usr and the rt3 directory within it (/usr/local/rt3). I then moved the entire html directory, created in 1. (above), to /usr/local/rt3. But again, after restarting httpd I could not see the Time Worked Report.

Thanks in advance,
WalidFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kenneth Crocker
Sent: terça-feira, 29 de Março de 2011 16:42
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Opps, that was supposed to be /local/html/Tools/Report. Sorry.

Kenn

Walid,

In step 4, you don’t mention editing the “Tabs” file with the changes
specified in the instructions.

In steps 5 & 6, those files should have been moved to
usr/share/rt3/local/html/Tools/Reports.

  1. The “Tabs” and “index.html” files must be modified & kept* in-sync* in
    order to see the option in the “Tabs” heading. That certainly explains why
    they both have the same paths for the same reports. You should compare the
    code between those two and make sure they look exactly like they should,
    according to the instructions.

  2. The “TimeWorkedReport.html” file has to be where the “Tabs” and
    "index.html" files are pointing to within the “path” shown.

Moving these files around to other directories will just frustrate you more
and distract you away from de-bugging the real problem.

If this doesn’t work, send me a list of the modified code for “Tabs” and
"index.html".

Kenn
LBNLOn Thu, Mar 31, 2011 at 1:18 AM, Walid Haider walid.haider@movensis.comwrote:

Hi Kenn,

Thanks for the tip regarding RT $home, I will definitely consider it.

I must be missing something, as I cannot see the Time Worked Report option
on the menu.

This is what I did:

  1.   Created a *local* directory within /usr/share/rt3, and then
    

created the /usr/share/rt3/local/html and /usr/share/rt3/local/html/*
Elements* directories.

  1.   Created the new file *SelectMultiQueue* (with the relevant
    

content) within /usr/share/rt3/local/html/Elements

  1.   Created …/rt3/local/*Tools*, …/rt3/local/Tools/*Reports*,* *and*
    

*…/rt3/local/Tools/Reports/*Elements *directories

  1.   Copied the *Tabs* file from
    

/usr/share/rt3/html/Tools/Reports/Elements/Tabs to
…/rt3/local/Tools/Reports/Elements

  1.   Copied the index.html file from
    

/usr/share/rt3/html/Tools/Reports/index.html to …/rt3/local/Tools/ and
edited the file accordingly

  1.   Created the *TimeWorkedReport.html*  (with the relevant content)
    

file in …/rt3/local/Tools/

  1.   I restarted httpd and logged into RT, but could not see  the
    

Timed Worked Report option on the menu

I then tried moving the index.html and TimeWorkedReport.html files from
/usr/share/rt3/local/html/Tools/Reports into
/usr/share/rt3/local/html/Tools/. But after restarting httpd, I still could
not see the Time Worked Report.

Finally, I tried creating the local directory in /usr and the rt3directory within it (/usr/local/rt3). I then moved the entire
*html *directory, created in 1. (above), to /usr/local/rt3. But again,
after restarting httpd I could not see the Time Worked Report.

Thanks in advance,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: terça-feira, 29 de Março de 2011 16:42

To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Opps, that was supposed to be /local/html/Tools/Report. Sorry.

Kenn

On Tue, Mar 29, 2011 at 8:39 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Walid,

Also, we used to have a different $home than /opt/rt3/ (in Solaris) and it
caused endless problems when trying to implement extensions. We decided
to just go to opt/rt3 and put it in VM and we’ve been sailing smoothly ever
since. Just a thought for you to consider.

Kenn
LBNL

On Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Walid,

Well, Wherever you have the …/Tools/Report/… you will need a
…/local/Tools/Report/ version to put “TimeWorkedReport”.

Kenn
LBNL

On Tue, Mar 29, 2011 at 7:00 AM, Walid Haider walid.haider@movensis.com wrote:

Hi Johan,

No, I do not. Should I go ahead and create it and then follow Kenn’s
instructions?

Regards,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Johan Sjöberg
Sent: terça-feira, 29 de Março de 2011 14:56

To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Do you have a /usr/local/rt3?

/Johan

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Walid Haider
Sent: den 29 mars 2011 15:20
To: Kenneth Crocker; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Kenn,

Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my
$home is /usr/share/rt3. My folder structure is different compared to what
you mention below, as I do not have a share directory within my RT $home.

Please advise if I should create the local directory within
/usr/share/rt3.

Thanks,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: segunda-feira, 28 de Março de 2011 17:33
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Walid,

What I mean is this; it is highly recommended that any changes you make
to RT code be done in a “local” version. RT will automatically look to
$Home/local/…/…/ (where $home is usually opt/rt3/) for any override
code
that an installation may have developed. In this example
(TimeWorkedReport), I copied the various /$home*/share/…/…
directories & files listed in the "readme’ for that report into a /$home/

local/*…/… version/copy of those directoryies & files. I did NOTmake any changes to any
/share/ version of RT code. This is recommended for a couple reasons;
the least of which it is easier to maintain later versions of RT without
wiping out your local code (provided you keep a copy of that code). Also,
industry wide for about the last 40 years, it has been considered a best
practice
to never mess with original code, but to provide a method that
allows you to use other code instead.

So, my advice is to first; return all /share/ code to it’s original state.
Then create $home*/local/*html/Tools/Reports directories in order to
copy/create the files mentioned in the “TimeWorkedReport” documentation.
That’s what I did:

  1. If it exists,type “/opt/rt3/local/html/Elements/” otherwise,
    create it.
  2. Copy the “delivered” file (from …/share/…) SelectQueue over to
    this directory with a the new name.
    A) Type “cp /opt/rt3/share/html/Elements/SelectQueue
    SelectMultiQueue”
    .
  3. Replace the code in “SelectMultiQueue” with the code specified for
    this file from the document the “TimeWorkedReport".
  4. If it exists, type “/opt/rt3/local/html/Tools/” , otherwise,
    create it.
  5. Create new directories:
    A) Create “Reports” directory within *“Tools”
    *B) Get into “Reports” directory.
    C) Create “Elements” directory within “Tools/Reports”
  6. Copy the “delivered” files (from …/share/…) (Tabs, index.html)
    over to the new directories:
    A) Copy the “Tabs” file over to “Tools/Reports/Elements”:
    1) Within “Elements”, type “cp
    /opt/rt3/share/html/Tools/Reports/Elements/Tabs .”
    .
    2) Go back 1 directory level to get to “/Tools/Reports”.
    3) Copy the “index.html” file over to “Tools/Reports” twice:
    a) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html .”
    .
    b) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html TimeWorkedReport.html”
    .
  7. Modify/Replace the code in *“Tabs”, “index.html” & “TimeWorkedReport”
    *with the code specified for these files from the document the “Time
    Worked Report”
    .

Anyway, This is the procedure I followed and I had absolutely no problems
AND I didn’t have to worry about Production being messed up.

Also, I’m in 3.8.7 so I made sure to follow the 3.8 instructions.

Hope this helps.

Kenn
LBNL

Hi Kenn,

Thanks for all the help - I finally managed to implement the Time Worked Report - the problem was when I copied the code for SelectMultiQueue from http://requesttracker.wikia.com/wiki/TimeWorkedReport, I did not realize there was a blank space for each line.

Regards,
WalidFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kenneth Crocker
Sent: quinta-feira, 31 de Março de 2011 18:35
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Walid,

In step 4, you don’t mention editing the “Tabs” file with the changes specified in the instructions.

In steps 5 & 6, those files should have been moved to usr/share/rt3/local/html/Tools/Reports.

  1. The “Tabs” and “index.html” files must be modified & kept in-sync in order to see the option in the “Tabs” heading. That certainly explains why they both have the same paths for the same reports. You should compare the code between those two and make sure they look exactly like they should, according to the instructions.

  2. The “TimeWorkedReport.html” file has to be where the “Tabs” and “index.html” files are pointing to within the “path” shown.

Moving these files around to other directories will just frustrate you more and distract you away from de-bugging the real problem.

If this doesn’t work, send me a list of the modified code for “Tabs” and “index.html”.

Kenn
LBNL

Walid,

I made a change to my version. Instead of “SuperUser” seeing all users, I
changed it to members of a particular group. My group managers didn’t like
the “SuperUser” right because they had to see way too much other stuff that
didn’t apply to their respective Queues, so I changed it for a specific
group.

Kenn
LBNLOn Tue, Apr 26, 2011 at 3:38 AM, Walid Haider walid.haider@movensis.comwrote:

Hi Kenn,

Thanks for all the help – I finally managed to implement the Time Worked
Report – the problem was when I copied the code for SelectMultiQueue from
http://requesttracker.wikia.com/wiki/TimeWorkedReport, I did not realize
there was a blank space for each line.

Regards,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: quinta-feira, 31 de Março de 2011 18:35

To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Walid,

In step 4, you don’t mention editing the “Tabs” file with the changes
specified in the instructions.

In steps 5 & 6, those files should have been moved to
usr/share/rt3/local/html/Tools/Reports.

  1. The “Tabs” and “index.html” files must be modified & kept* in-sync* in
    order to see the option in the “Tabs” heading. That certainly explains why
    they both have the same paths for the same reports. You should compare the
    code between those two and make sure they look exactly like they should,
    according to the instructions.

  2. The “TimeWorkedReport.html” file has to be where the “Tabs” and
    "index.html" files are pointing to within the “path” shown.

Moving these files around to other directories will just frustrate you more
and distract you away from de-bugging the real problem.

If this doesn’t work, send me a list of the modified code for “Tabs” and
"index.html".

Kenn
LBNL

On Thu, Mar 31, 2011 at 1:18 AM, Walid Haider walid.haider@movensis.com wrote:

Hi Kenn,

Thanks for the tip regarding RT $home, I will definitely consider it.

I must be missing something, as I cannot see the Time Worked Report option
on the menu.

This is what I did:

  1.   Created a *local* directory within /usr/share/rt3, and then
    

created the /usr/share/rt3/local/html and /usr/share/rt3/local/html/*
Elements* directories.

  1.   Created the new file *SelectMultiQueue* (with the relevant
    

content) within /usr/share/rt3/local/html/Elements

  1.   Created …/rt3/local/*Tools*, …/rt3/local/Tools/*Reports*,* *and*
    

*…/rt3/local/Tools/Reports/*Elements *directories

  1.   Copied the *Tabs* file from
    

/usr/share/rt3/html/Tools/Reports/Elements/Tabs to
…/rt3/local/Tools/Reports/Elements

  1.   Copied the index.html file from
    

/usr/share/rt3/html/Tools/Reports/index.html to …/rt3/local/Tools/ and
edited the file accordingly

  1.   Created the *TimeWorkedReport.html*  (with the relevant content)
    

file in …/rt3/local/Tools/

  1.   I restarted httpd and logged into RT, but could not see  the
    

Timed Worked Report option on the menu

I then tried moving the index.html and TimeWorkedReport.html files from
/usr/share/rt3/local/html/Tools/Reports into
/usr/share/rt3/local/html/Tools/. But after restarting httpd, I still could
not see the Time Worked Report.

Finally, I tried creating the local directory in /usr and the rt3directory within it (/usr/local/rt3). I then moved the entire
*html *directory, created in 1. (above), to /usr/local/rt3. But again,
after restarting httpd I could not see the Time Worked Report.

Thanks in advance,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: terça-feira, 29 de Março de 2011 16:42

To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Opps, that was supposed to be /local/html/Tools/Report. Sorry.

Kenn

On Tue, Mar 29, 2011 at 8:39 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Walid,

Also, we used to have a different $home than /opt/rt3/ (in Solaris) and it
caused endless problems when trying to implement extensions. We decided
to just go to opt/rt3 and put it in VM and we’ve been sailing smoothly ever
since. Just a thought for you to consider.

Kenn
LBNL

On Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:

Walid,

Well, Wherever you have the …/Tools/Report/… you will need a
…/local/Tools/Report/ version to put “TimeWorkedReport”.

Kenn
LBNL

On Tue, Mar 29, 2011 at 7:00 AM, Walid Haider walid.haider@movensis.com wrote:

Hi Johan,

No, I do not. Should I go ahead and create it and then follow Kenn’s
instructions?

Regards,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Johan Sjöberg
Sent: terça-feira, 29 de Março de 2011 14:56

To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Do you have a /usr/local/rt3?

/Johan

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Walid Haider
Sent: den 29 mars 2011 15:20
To: Kenneth Crocker; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Kenn,

Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my
$home is /usr/share/rt3. My folder structure is different compared to what
you mention below, as I do not have a share directory within my RT $home.

Please advise if I should create the local directory within
/usr/share/rt3.

Thanks,

Walid

From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: segunda-feira, 28 de Março de 2011 17:33
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked Report

Walid,

What I mean is this; it is highly recommended that any changes you make
to RT code be done in a “local” version. RT will automatically look to
$Home/local/…/…/ (where $home is usually opt/rt3/) for any override
code
that an installation may have developed. In this example
(TimeWorkedReport), I copied the various /$home*/share/…/…
directories & files listed in the "readme’ for that report into a /$home/

local/*…/… version/copy of those directoryies & files. I did NOTmake any changes to any
/share/ version of RT code. This is recommended for a couple reasons;
the least of which it is easier to maintain later versions of RT without
wiping out your local code (provided you keep a copy of that code). Also,
industry wide for about the last 40 years, it has been considered a best
practice
to never mess with original code, but to provide a method that
allows you to use other code instead.

So, my advice is to first; return all /share/ code to it’s original state.
Then create $home*/local/*html/Tools/Reports directories in order to
copy/create the files mentioned in the “TimeWorkedReport” documentation.
That’s what I did:

  1. If it exists,type “/opt/rt3/local/html/Elements/” otherwise,
    create it.
  2. Copy the “delivered” file (from …/share/…) SelectQueue over to
    this directory with a the new name.
    A) Type “cp /opt/rt3/share/html/Elements/SelectQueue
    SelectMultiQueue”
    .
  3. Replace the code in “SelectMultiQueue” with the code specified for
    this file from the document the “TimeWorkedReport".
  4. If it exists, type “/opt/rt3/local/html/Tools/” , otherwise,
    create it.
  5. Create new directories:
    A) Create “Reports” directory within *“Tools”
    *B) Get into “Reports” directory.
    C) Create “Elements” directory within “Tools/Reports”
  6. Copy the “delivered” files (from …/share/…) (Tabs, index.html)
    over to the new directories:
    A) Copy the “Tabs” file over to “Tools/Reports/Elements”:
    1) Within “Elements”, type “cp
    /opt/rt3/share/html/Tools/Reports/Elements/Tabs .”
    .
    2) Go back 1 directory level to get to “/Tools/Reports”.
    3) Copy the “index.html” file over to “Tools/Reports” twice:
    a) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html .”
    .
    b) Within “Tools/Reports”, type “cp
    /opt/rt3/share/html/Tools/index.html TimeWorkedReport.html”
    .
  7. Modify/Replace the code in *“Tabs”, “index.html” & “TimeWorkedReport”
    *with the code specified for these files from the document the “Time
    Worked Report”
    .

Anyway, This is the procedure I followed and I had absolutely no problems
AND I didn’t have to worry about Production being messed up.

Also, I’m in 3.8.7 so I made sure to follow the 3.8 instructions.

Hope this helps.

Kenn
LBNL