[rt-users] Order of custom field updates

[Woody - Wild Thing Safaris]

Hi folks,

I have a scrip that runs onCustomFieldChange, and it creates another
ticket using data from other custom fields.

eg

Payment amount  - value
Payment currency - select
Payment destination  - select
Payment type - select

A scrip triggers on change of Payment type, but when the new ticket is
created, amount and currency are defined, but destination is not set so
i get something like

Incoming Payment of x GBP - .

instead of

Incoming Payment of  GBP - Current account

I have checked the id number of the custom fields thinking maybe they
update in id order, but Payment Type is the lowest, and Payment
Destination is not the highest. Payment type is the last in the list
that's displayed, so I'm not sure how the order of field updates is decided.

Can anyone suggest a solution or provide any info on how the order of
field updates is defined and how i can change it (presumably by changing
field names or deleting and re-adding?)

thanks

--
---
Richard Wood (Woody)
Managing Director
Wild Thing Safaris Ltd.
PO BOX 34514 DSM
Office: +255 (0) 222 617 166
Office Mobile: +255 (0) 773 503 502
Direct: +255 657 799 468
Skype: woody1tz
http://wildthingsafaris.com

[rt-users] Create Queue / Create Group Access

[Tim Gustafson]

What is the "best practice" way to give non-superusers access to
create groups and queues, and then manage the groups and queues they
create, but not groups and queues that were created by other users?

-- 

Tim Gustafson
t...@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A

[rt-users] Howto overwrite user preferences

[Sternberger, Sven]

Hello!

we will upgrade soon our RT from 3.8.7 to 4.2.9, and
I would like to initially set the preference
for Theme  on System default (in our case now rudder)

I found that the Preferences are stored in the DB in the table
Attributes with the Name Pref-RT::System-1, but is there a way 
to override/alter them?

In the content I only see something like

BQkDARcDMTIwHFNlYXJjaFJlc3VsdHNSZWZyZXNoSW50ZXJ2YWw=

regards!

Sven

[rt-users] Outgoing email text of a closing incident

[Tamás, Szép]

Hello all,

where can I find and modify the text of the outgoing email when I close
a whole Incident?

Best regards,
Tamas Szep
GovCERT-Hungary

Re: [rt-users] quick-set Starts date

[Brumm, Torsten / Kuehne + Nagel / Ham GI-ID]

Hi Alex,
sounds good to me, waiting to see your changes

Torsten

Von: Alex Peters [mailto:a...@peters.net]
Gesendet: Mittwoch, 3. Dezember 2014 08:39
An: Brumm, Torsten / Kuehne + Nagel / Ham GI-ID
Cc: rt-users@lists.bestpractical.com
Betreff: Re: [rt-users] quick-set Starts date

This is a great starting point!  Thanks very much.

I intend to modify the code you've provided in the following ways:

  *   provide an option not to stall the tickets
  *   use free-form dates and times (e.g. "8pm today", "midnight tomorrow")
  *   define the desired buttons via RT_SiteConfig.pm
  *   make the dates/times relative to the time of the button being pressed, 
not the time of the Display page being loaded
When I get around to that, and if I can do these changes in a way that would 
make sense for that plugin, I'll gladly send you a GitHub pull request.

2014-12-02 22:01 GMT+09:00 Brumm, Torsten / Kuehne + Nagel / Ham GI-ID 
mailto:torsten.br...@kuehne-nagel.com>>:
Hi Alex,
just spent a few minutes to change the original RT-Extension-DueButtons to 
StartsButtons:

https://github.com/tbrumm/RT-Extension-StartsButtons

Have fun.

Von: rt-users 
[mailto:rt-users-boun...@lists.bestpractical.com]
 Im Auftrag von Alex Peters
Gesendet: Dienstag, 2. Dezember 2014 03:23
An: rt-users@lists.bestpractical.com
Betreff: [rt-users] quick-set Starts date

I want to be able to quickly adjust a ticket's Starts date from the ticket's 
Display view without going to the ticket's Dates page and manually entering the 
date.

For example, having a "Starts" top-level menu item next to "Actions" with 
sub-entries "tomorrow morning," "next week" etc. would achieve this nicely.

Has anyone already done something like this?  Any recommended approaches?  Is 
there a best-practice way for submitting a POST request from that menu, or 
would I have to do it as a GET request?  Is anyone aware of a plugin that works 
in a similar manner?  Any pointers on which callbacks I should target?

Kühne + Nagel (AG & Co.) KG
Rechtsform: Kommanditgesellschaft, Bremen HRA 21928, USt-IdNr.: DE 812773878.
Geschäftsleitung Kühne + Nagel (AG & Co.) KG: Reiner Heiken (Vors.), Dirk 
Blesius, Martin Brinkmann, Holger Ketz, Jan-Hendrik Köstergarten, Christian 
Marnetté, Christian Solf, Jens Wollesen.
Persönlich haftende Gesellschafterin: Kühne & Nagel A.G., Rechtsform: 
Aktiengesellschaft nach luxemburgischem Recht, HR-Nr.: B 18745, 
Geschäftsführendes Verwaltungsratsmitglied: Karl Gernandt.
Geschäftsleitung Region Westeuropa: Yngve Ruud (Vors.), Hans-Georg Brinkmann 
(Stellv.), Richard Huhn, Björn Johansson, Bruno Mang, Stefan Paul, Tim 
Scharwath, Dominic Edmonds, Peder Winther.

Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen 
Spediteursbedingungen (ADSp), jeweils neuester Fassung. Wir verweisen 
insbesondere auf die vom Gesetz abweichenden Haftungsbeschränkungen von Ziffer 
23 und 24 ADSp. Den vollständigen Text der ADSp übersenden wir Ihnen gerne auf 
Anfrage und können Sie auch unter http://www.kuehne-nagel.com einsehen. 
Ergänzend wird vereinbart, dass (1) Ziffer 27 ADSp im Rahmen internationaler 
Übereinkommen weder unsere Haftung noch die Zurechnung des Verschuldens von 
Leuten und sonstigen Dritten zu Gunsten des Auftraggebers erweitert, und (2) 
wir in den im deutschen Seehandelsrecht aufgeführten Fällen des nautischen 
Verschuldens oder Feuer an Bord nur für eigenes Verschulden und (3) im Sinne 
der CMNI genannten Voraussetzungen nicht für nautisches Verschulden, Feuer an 
Bord oder Mängel des Schiffes haften.

Re: [rt-users] plugins link to module file, not package file

[Alex Peters]

I think I might be missing something crucial in what you are saying/asking.

Linking to the main module within a distribution is a very common practice,
because that module is likely to have the most relevant documentation for
that distribution.

The distribution is clearly linked to on the page of every module belonging
to a particular distribution.

"Asking the user to edit the URL in their browser window to be able to find
the extension to download doesn’t make a lot of sense" is essentially a
fallacy, because:

   1. the download link for the extension is available on that very page;
   and
   2. the home page for the extension itself (which in my opinion is
   generally far less informational anyway) is available as a link on that
   very page.

Can you please rephrase why you feel that the links in the directory should
be changed?  Your assertion that these links are "broken" in their current
form is confusing to me.

On 3 December 2014 at 18:40, Jo Rhett  wrote:

> As I said below, in the Extensions directory the links are broken. For
> example,
>
> Homepage link takes you to:
>>
>> http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm
>>
>> If you’re a bit tired and under-caffeniated, or just plain new to RT, it
>> may not be clear to you that you need to remove a bunch from the URL to
>> find the extension package. In my opinion, it would be much better to link
>> to the package instead of the module file, like so:
>>
> http://search.cpan.org/dist/RT-Extension-MandatorySubject/
>>
>
> As I just said, asking the user to edit the URL in their browser window to
> be able to find the extension to download doesn’t make a lot of sense. The
> links in the directory should be fixed.
>
> On Dec 2, 2014, at 11:34 PM, Alex Peters  wrote:
>
> Could you please clarify what you're asking here?  How to install the
> plugins?
>
> The plugins can be installed like any other CPAN module.  Given a link to
> a specific .pm file:
>
>
> http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm
>
> you can hit the Download link on the right side of the page to receive a
> .tar.gz file of the distribution, which can either be fed directly into the
> cpan or cpanm utilities, or unpacked and installed manually using
> Makefile.PL and make.
>
> With RT extensions, you may find it useful to set environment variable
> RTHOME to the root directory of your RT installation before installing the
> plugin:
>
> $ RTHOME=/opt/rt-4.2.7 cpanm RT-Extension-MandatorySubject-0.05.tar.gz
>
> On 3 December 2014 at 16:19, Jo Rhett  wrote:
>
>> Hey, dunno if this got overlooked during the short vacation week. This is
>> a pretty serious issue…  asking users to manually hack up the URL in their
>> browser bar is not accessible.
>>
>> On Nov 26, 2014, at 2:22 PM, Jo Rhett  wrote:
>>
>> Hey guys and gals, been a long time.
>>
>> I’m doing an upgrade from 3.8.5 to 4.2. It seems to be going well. I’m
>> liking the changes. Other than some confusion about what order to do things
>> in (see my other message) the one thing I can’t seem to wrap my head around
>> is the new plugin setup.
>>
>> First, yay! I like the idea of what you’ve done with plugins, keeping
>> them local and the simplified syntax in RT_SiteConfig.pm.
>>
>> [in which I wander in the wrong direction… read and giggle]
>>
>> However, I can’t find any plugins other than yours which are built in
>> these new packages you document at
>> https://www.bestpractical.com/docs/rt/4.2/writing_extensions.html
>>
>> What is the fallback method for installing the other style modules? How
>> do I get from a .pm file to an installed module. Can I manually create the
>> directory structures and copy these into place? I see some details there
>> but it doesn’t inspire confidence that everything I need to know is there.
>> A breakout of the directory structure would be really helpful.
>>
>> [forehead slap]
>>
>> I was almost done with this e-mail when I realized the problem.  If you
>> go to http://bestpractical.com/rt/extensions.html and you find the
>> extension you are looking for, the link to the Homepage for the extension
>> actually links to the main module, and not to the extension package.
>> Example for one
>>
>> Homepage link takes you to:
>>
>> http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm
>>
>> If you’re a bit tired and under-caffeniated, or just plain new to RT, it
>> may not be clear to you that you need to remove a bunch from the URL to
>> find the extension package. In my opinion, it would be much better to link
>> to the package instead of the module file, like so:
>> http://search.cpan.org/dist/RT-Extension-MandatorySubject/
>>
>> I did some random spot checking, and this appears to be true for every
>> module shown there.
>>
>> --
>> Jo Rhett
>> +1 (415) 999-1798
>> Skype: jorhett
>> Net Consonance : net philanthropy to improve open source and
>> internet pr

Re: [rt-users] plugins link to module file, not package file

[Christian Loos]

Am 03.12.2014 um 10:40 schrieb Jo Rhett:
> As I just said, asking the user to edit the URL in their browser window
> to be able to find the extension to download doesn’t make a lot of
> sense. The links in the directory should be fixed.

Why do you want to download the extension?
You can install them by cpan with
cpan RT::Extension::MandatorySubject

Chris

Re: [rt-users] plugins link to module file, not package file

[Jo Rhett]

As I said below, in the Extensions directory the links are broken. For example,

Homepage link takes you to:

http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm

If you’re a bit tired and under-caffeniated, or just plain new to RT, it may 
not be clear to you that you need to remove a bunch from the URL to find the 
extension package. In my opinion, it would be much better to link to the 
package instead of the module file, like so:
http://search.cpan.org/dist/RT-Extension-MandatorySubject/

As I just said, asking the user to edit the URL in their browser window to be 
able to find the extension to download doesn’t make a lot of sense. The links 
in the directory should be fixed.

On Dec 2, 2014, at 11:34 PM, Alex Peters  wrote:
> Could you please clarify what you're asking here?  How to install the plugins?
> 
> The plugins can be installed like any other CPAN module.  Given a link to a 
> specific .pm file:
> 
> http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm
> 
> you can hit the Download link on the right side of the page to receive a 
> .tar.gz file of the distribution, which can either be fed directly into the 
> cpan or cpanm utilities, or unpacked and installed manually using Makefile.PL 
> and make.
> 
> With RT extensions, you may find it useful to set environment variable RTHOME 
> to the root directory of your RT installation before installing the plugin:
> 
> $ RTHOME=/opt/rt-4.2.7 cpanm RT-Extension-MandatorySubject-0.05.tar.gz
> 
> On 3 December 2014 at 16:19, Jo Rhett  wrote:
> Hey, dunno if this got overlooked during the short vacation week. This is a 
> pretty serious issue…  asking users to manually hack up the URL in their 
> browser bar is not accessible.
> 
> On Nov 26, 2014, at 2:22 PM, Jo Rhett  wrote:
>> Hey guys and gals, been a long time.
>> 
>> I’m doing an upgrade from 3.8.5 to 4.2. It seems to be going well. I’m 
>> liking the changes. Other than some confusion about what order to do things 
>> in (see my other message) the one thing I can’t seem to wrap my head around 
>> is the new plugin setup.
>> 
>> First, yay! I like the idea of what you’ve done with plugins, keeping them 
>> local and the simplified syntax in RT_SiteConfig.pm.
>> 
>> [in which I wander in the wrong direction… read and giggle]
>> 
>> However, I can’t find any plugins other than yours which are built in these 
>> new packages you document at 
>> https://www.bestpractical.com/docs/rt/4.2/writing_extensions.html
>> 
>> What is the fallback method for installing the other style modules? How do I 
>> get from a .pm file to an installed module. Can I manually create the 
>> directory structures and copy these into place? I see some details there but 
>> it doesn’t inspire confidence that everything I need to know is there. A 
>> breakout of the directory structure would be really helpful.
>> 
>> [forehead slap]
>> 
>> I was almost done with this e-mail when I realized the problem.  If you go 
>> to http://bestpractical.com/rt/extensions.html and you find the extension 
>> you are looking for, the link to the Homepage for the extension actually 
>> links to the main module, and not to the extension package. Example for one
>> 
>> Homepage link takes you to:
>>  
>> http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm
>> 
>> If you’re a bit tired and under-caffeniated, or just plain new to RT, it may 
>> not be clear to you that you need to remove a bunch from the URL to find the 
>> extension package. In my opinion, it would be much better to link to the 
>> package instead of the module file, like so:
>>  http://search.cpan.org/dist/RT-Extension-MandatorySubject/
>> 
>> I did some random spot checking, and this appears to be true for every 
>> module shown there.
>> 
>> -- 
>> Jo Rhett
>> +1 (415) 999-1798
>> Skype: jorhett
>> Net Consonance : net philanthropy to improve open source and internet 
>> projects.
>> 
> 
> -- 
> Jo Rhett
> +1 (415) 999-1798
> Skype: jorhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
> 
> 

-- 
Jo Rhett
+1 (415) 999-1798
Skype: jorhett
Net Consonance : net philanthropy to improve open source and internet projects.