Address field behavior with RT 4.0.1 upgrade

RT Users
1

We just upgraded to RT 4.0.1 and we’ve noticed that when creating or
editing tickets, the Requestor, Cc, and Admin Cc field seems to have
remember any e-mail address which has been part of any ticket somewhere
along the line.

How do you disable this behavior? We really don’t want auto-search and
completion for these fields. The main reason is that we use RT
internally and limit access from the outside world to our RT queues.
It’s extremely easy to add addresses to these fields now that it seems
to pick up any e-mail address in the system.

Is it possible to turn this off within RT so it’s not seeming to collect
e-mail addresses in this fashion?

Regards,
Max

2

Ok, so I found where this is a new feature with the 4.0.1 release. I see
where to adjust what fields and how you want the fields to behave.

But, I see no place or how to make this go back to the old way of a
“text” field.

Sorry to keep responding to myself.

I realize what’s going on here now is that the Requester, Cc, and Admin
Cc fields are using Autocomplete on both privileged and unprivileged users.

When a user in the past has created a ticket, they get an unprivileged
user account created automatically.

Is there a way to limit the Autocomplete to only search for privileged
users in the system?

Thanks,
Max

3

We just upgraded to RT 4.0.1 and we’ve noticed that when creating or
editing tickets, the Requestor, Cc, and Admin Cc field seems to have
remember any e-mail address which has been part of any ticket somewhere
along the line.

How do you disable this behavior? We really don’t want auto-search and
completion for these fields. The main reason is that we use RT
internally and limit access from the outside world to our RT queues.
It’s extremely easy to add addresses to these fields now that it seems
to pick up any e-mail address in the system.

Is it possible to turn this off within RT so it’s not seeming to collect
e-mail addresses in this fashion?

Ok, so I found where this is a new feature with the 4.0.1 release. I see
where to adjust what fields and how you want the fields to behave.

But, I see no place or how to make this go back to the old way of a
“text” field.

Regards,
Max

4

Ok, so I found where this is a new feature with the 4.0.1 release. I see
where to adjust what fields and how you want the fields to behave.

But, I see no place or how to make this go back to the old way of a
“text” field.

Sorry to keep responding to myself.

I realize what’s going on here now is that the Requester, Cc, and
Admin Cc fields are using Autocomplete on both privileged and
unprivileged users.

When a user in the past has created a ticket, they get an
unprivileged user account created automatically.

Is there a way to limit the Autocomplete to only search for
privileged users in the system?

Thanks,
Max

What about:

Set($EmailCompletionLdapDisabled, 1);

Since whether a user is privileged or not is only in the RT DB.
You may need to edit the module code to restrict the results further.

Ken

5

What about:

Set($EmailCompletionLdapDisabled, 1);

Since whether a user is privileged or not is only in the RT DB.
You may need to edit the module code to restrict the results further.

No luck there.

Ok, thanks for the hint. I found the module paths. I’ll have to consult
with our resident Perl guru to see about that.

I appreciate it.

Regards,
Max

6

Is there a way to limit the Autocomplete to only search for privileged
users in the system?

The autocomplete code has logic for doing this, but it’s not exposed as
a configuration option and is only used internally in certain parts of
the admin UI where it makes sense to have only privileged users. We’d
certainly take a small patch to expose it in the config as well.

I believe we mean to do this for a future 4.0.x release.

But, I see no place or how to make this go back to the old way of a “text” field.

Additionally, we might take a patch to make the entire feature
enabled/disabled at the config level, but that would be a little bit
more work.

Thomas

7

Ok, so I found where this is a new feature with the 4.0.1 release. I see
where to adjust what fields and how you want the fields to behave.

But, I see no place or how to make this go back to the old way of a
“text” field.

Sorry to keep responding to myself.

I realize what’s going on here now is that the Requester, Cc, and
Admin Cc fields are using Autocomplete on both privileged and
unprivileged users.

When a user in the past has created a ticket, they get an
unprivileged user account created automatically.

Is there a way to limit the Autocomplete to only search for
privileged users in the system?

Thanks,
Max

What about:

Set($EmailCompletionLdapDisabled, 1);

Since whether a user is privileged or not is only in the RT DB.
You may need to edit the module code to restrict the results further.

Ken - that’s the config for RTx-EmailAddress, not for RT core.

As Tom notes later in the thread, we’d take a patch to add a config
for this to core.

-kevin

8

Ok, so I found where this is a new feature with the 4.0.1 release. I see
where to adjust what fields and how you want the fields to behave.

But, I see no place or how to make this go back to the old way of a
“text” field.

Sorry to keep responding to myself.

I realize what’s going on here now is that the Requester, Cc, and
Admin Cc fields are using Autocomplete on both privileged and
unprivileged users.

When a user in the past has created a ticket, they get an
unprivileged user account created automatically.

Is there a way to limit the Autocomplete to only search for
privileged users in the system?

Thanks,
Max

What about:

Set($EmailCompletionLdapDisabled, 1);

Since whether a user is privileged or not is only in the RT DB.
You may need to edit the module code to restrict the results further.

Ken - that’s the config for RTx-EmailAddress, not for RT core.

As Tom notes later in the thread, we’d take a patch to add a config
for this to core.

-kevin

Oops, I forgot that that had been integrated in RT 4. We are still
on 3.8.

Ken

9

Ken - that’s the config for RTx-EmailAddress, not for RT core.

As Tom notes later in the thread, we’d take a patch to add a config
for this to core.

Thanks, Tom and Kevin.

Since I’m not a programmer, I’ll speak to the Perl guy at my employer
and see if this is feasible for him to do.

Thanks for the information!

Regards,
Max

10

Hi List, Thomas,
has this already bin fixed or implemented already? I just read the RT Announcements up to 4.0.22 and couldn’t find any hint.

TorstenVon: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] Im Auftrag von Thomas Sibley
Gesendet: Dienstag, 12. Juli 2011 23:44
An: rt-users@lists.bestpractical.com
Betreff: Re: [rt-users] Address field behavior with RT 4.0.1 upgrade

Is there a way to limit the Autocomplete to only search for privileged
users in the system?

The autocomplete code has logic for doing this, but it’s not exposed as a configuration option and is only used internally in certain parts of the admin UI where it makes sense to have only privileged users. We’d certainly take a small patch to expose it in the config as well.

I believe we mean to do this for a future 4.0.x release.

But, I see no place or how to make this go back to the old way of a “text” field.

Additionally, we might take a patch to make the entire feature enabled/disabled at the config level, but that would be a little bit more work.

Thomas

2011 Training: http://bestpractical.com/services/training.html

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.

11

has this already bin fixed or implemented already? I just read the RT Announcements up to 4.0.22 and couldn’t find any hint.

No.

In 4.2, privileged triggers using a data attribute of the input, which
is something you would be able to add on using JS, so we’re unlikely
to take anything for this in 4.0, since it wouldn’t be fixing a bug.

-kevin