Given no answers yet, it seems that either no one can replicate this (in
which case a works for me would prompt me to debug further) or no one has
attempted to remove due dates from tickets in v4.2.5.
I'll assume the latter and file a bug report.
On 24 June 2014 21:40, Alex Peters
I have achieved this in the past by temporarily moving the ticket to a
queue without resolve scrips, resolving the ticket then moving it back to
the correct queue. You could automate this by creating a Silent Resolve
queue, and having a scrip to resolve the ticket and then move it back to
the
RT doesn't notify two users if they have both entered an editing screen for
the same ticket, as you've discovered.
I'm not sure that many people generally see this as an issue though. If
two people add commentary to the ticket, both comments are kept. If two
people edit a ticket's fields at the
RT::Extension::RepeatTicket doesn't suit my specific needs, so I'm
implementing a solution using scrips and templates.
I should have given more regard to your earlier remark about the time
parsing configuration options—after playing with Time::ParseDate
separately, I determined that PREFER_FUTURE
Am 30.06.2014 08:04, schrieb Alex Peters:
Given no answers yet, it seems that either no one can replicate this (in
which case a works for me would prompt me to debug further) or no one
has attempted to remove due dates from tickets in v4.2.5.
I'll assume the latter and file a bug report.
Am 27.06.2014 23:02, schrieb Al Joslin:
I was asked by one of my users, what happens if two people are editing a
ticket at the same time ?
Our current system, that I'm trying to replace, tells users when another user
is editing the same ticket
I tried editing one ticket with two users
Thank you, but entering 0 does not work for me.
On 30/06/2014 5:30 pm, Christian Loos cl...@netcologne.de wrote:
Am 30.06.2014 08:04, schrieb Alex Peters:
Given no answers yet, it seems that either no one can replicate this (in
which case a works for me would prompt me to debug further) or
Does anyone have an example script I can use for reference? I have looked
everywhere and cannot seem to find any examples of how to go about using it
implementing it. I'm relatively new to RT and have never used perl until a
month ago.
So still trying to get to grips with it.
--
View this
I just couldn't believe that something like this could be broken but
indeed this works in 4.2.4 and is broken in 4.2.5.
I think this is related to this commit:
https://github.com/bestpractical/rt/commit/c4f7c8f
Especially the change to RT::Date-Unix as I see this the logs if I enter 0:
Passed a
Hello,
I have following problem:
root@rt:~# rt-mailgate --debug --action correspond --url=
https://localhost/rt --queue General /root/test.msg
/usr/bin/rt-mailgate: temp file is '/tmp/4iP43YcvGf/qapxKbbAkW'
/usr/bin/rt-mailgate: connecting to
https://localhost/rt/REST/1.0/NoAuth/mail-gateway
An
Hello,
I have following problem:
root@rt:~# rt-mailgate --debug --action correspond --url=
https://localhost/rt --queue General /root/test.msg
/usr/bin/rt-mailgate: temp file is '/tmp/4iP43YcvGf/qapxKbbAkW'
/usr/bin/rt-mailgate: connecting to
https://localhost/rt/REST/1.0/NoAuth/mail-gateway
An
Replace in the URL parameter to rt-mailgate localhost with the FQDN.
Chris
Am 30.06.2014 11:17, schrieb DD DD:
Hello,
I have following problem:
root@rt:~# rt-mailgate --debug --action correspond
--url=https://localhost/rt --queue General /root/test.msg
/usr/bin/rt-mailgate: temp file
It was a marketing bullet point that was granted larger significance than it
deserved in my tired mind
It's importance may yet be inflated by my users or management, but I think RT's
other strengths will win through
thanks,
al;
On Jun 30, 2014, at 2:35 AM, Alex Peters a...@peters.net wrote:
Please keep replies to the list.
Which RT version are you using?
Because your apache making a redirect and rt-mailgate following
redirects only in RT 4.2.4 and newer.
Chris
Am 30.06.2014 12:09, schrieb DD DD:
root@rt:~# wget https://HIDDEN/rt
--2014-06-30 12:04:42-- https://HIDDEN/rt
on old and new server there runs 4.0.7
new machine:
root@rt:~# wget https://127.0.0.1/rt
--2014-06-30 12:24:15-- https://127.0.0.1/rt
Connecting to 127.0.0.1:443... connected.
The certificate's owner does not match hostname `127.0.0.1'
root@rt:~# wget https://localhost/rt
--2014-06-30
I'm seeing a 'Cannot load ticket' error message when clicking on a link
to a ticket in a notification e-mail that I have received. It is ticket
#4546 that is failing.
I am using RT 3.8.14 with RTIR 2.6.1
I have debugging turned on and I am seeing the following in my logs:
[Sat Jun 28 11:28:27
Anybody have any suggestions for this? Thanks.
On Mon, 23 Jun 2014, Milt Epstein wrote:
Greetings.
I'm trying to customize the 10 newest uowned tickets search (the one
that appears on the main page by default, I believe). I get to the
page to edit the predefined Search - Unowned Tickets
I don't believe that you can achieve this with Ticket SQL, but there is
another potential solution:
You mention that the users are in groups for the queues relevant to them.
If you configure RT so that the users can't see tickets in queues whose
groups the users don't belong to, you would get
I agree that the misbehaviour is caused by the commit you reference here.
I believe however that the problem is caused by the change to the
ProcessTicketDates method in RT::Interface::Web.
The method now erroneously skips adjusting the date if the date is not
set—even if explicitly not set by
Thanks Kevin.
You are correct. For example JAWS and NVDA screen readers don't seem to know
how to speak the entity darr; (down arrow). Now that I see what's actually
happening I wonder if this should be fixed in the screen reader configuration.
Interestingly JAWS doesn't speak any of the
Hi Kevin.
This fixes the problem but I can't figure out where on our server to make the
change so that I can test the result. I tested on a simple, local file but when
I change our server location which happens to be
/opt/rt4/share/html/Widgets/SelectionBox It doesn't seem to make any
On Mon, Jun 30, 2014 at 05:27:20PM +, Keith Creasy wrote:
This fixes the problem but I can't figure out where on our server to
make the change so that I can test the result. I tested on a simple,
local file but when I change our server location which happens to be
No, I am not. This is probably what's happening. Thanks.
Keith
-Original Message-
From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of
Kevin Falcone
Sent: Monday, June 30, 2014 5:28 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Help with
Thanks for that suggestion. In fact, what you say makes sense, and
does work for the most part. But, we have a certain number of admin
users (such as myself), who can see tickets in multiple queues. I was
trying to set up something that would work for those users (we have
certain queues that
Another option for those admin users is to just not use that default
unowned tickets search, but instead replace that component of each admin
user's page with an appropriate saved search.
Depending on how frequently your admin users need to access all queues, and
if it makes sense in your
25 matches
Mail list logo
