hello,
We are using RT 4.4 and using the external authentication mechanism from a
remote DB to authenticate the user. To enable others to create ticket we
have enabled *AutoCreateNonExternalUsers*. But any mails from outside gets
the response.
*"You do not have permission to communicate with RT".
Hi Aniket,
You must configure "queue everyone privilege" to permit them to create
ticket.
Thank you.
2017-01-11 11:47 GMT+01:00 aniket tripathy :
> hello,
>
> We are using RT 4.4 and using the external authentication mechanism from a
> remote DB to authenticate the user. To enable others to cre
Hello!
We are using rt4.4.1 with the now build-in Assets. When bulk-updating a
custom field value for 2 Assets the following Error is logged and the
update fails:
[27811] [Wed Jan 11 13:35:52 2017] [warning]: Use of uninitialized value
$1 in hash element at /opt/rt4/sbin/../lib/RT/Interface/Web.p
Hi all,
Someone just asked me if I could add a feature to our RT installation, but
I don't know how to go about it.
In our customer service queue, we have a custom field for the order number
to which the ticket refers. Sometimes, two different reps will start
working on the same order without real
Sent from Mail for Windows 10
Hi Michael,
Line 183 of /opt/rt4/share/html/Asset/Search/Bulk.html seems to be the
problem, if you comment it out
the bulk update works.
# push @tmp_res, ProcessObjectCustomFieldUpdates( Object => $asset,
ARGSRef => \%ARGS );
I'm suspect that line 183 shouldn't be here as the customfields
Hi,
We are using RT 4.2.12. We noticed that the indexation stopped working.
When trying to run the indexer manually, I would get:
[11238] [Wed Jan 11 19:53:56 2017] [warning]: DBD::mysql::st execute
failed: MySQL server has gone away at /opt/rt4/sbin/rt-fulltext-indexer
line 216. (/opt/rt4/sbin/r
On Wed, 11 Jan 2017 15:17:53 -0500
François Meehan wrote:
> We are using RT 4.2.12. We noticed that the indexation stopped working.
> When trying to run the indexer manually, I would get:
>
> [11238] [Wed Jan 11 19:53:56 2017] [warning]: DBD::mysql::st execute
> failed: MySQL server has gone away