[rt-users] RT putes socket in to CLOSE_WAIT

[Asanka Gunasekera]

Hi All, I just got RT installed and below are the details

OS - CentOS release 6.5 (Final)
Apache - httpd-2.2.31
mod_perl - mod_perl-2.0.9
perl - perl-5.22.0
RT - rt-4.2.11

Once I log in to the system and click on some button, menu or any link I can 
see there is a new socket opend and the old one is put on CLOSE_WAIT state and 
this accumulates as below. 

tcp1  0 x.x.x.x:80  y.y.y.y:58815  CLOSE_WAIT  
26371/../bin/httpd

Please let me know what information is required to find a solution for this and 
is this a bug in the new version with my combination of software versions

Thanks and Best Regards

Re: [rt-users] RT Approvals

[Todd Wade]

On 9/11/15 9:47 AM, Kobus Bensch wrote:

I have setup approvals following this doc:
https://www.bestpractical.com/docs/rt/4.2.12/customizing/approvals.html.

I would like to setup multiple approvers based on a value in a custom
field. Is this possible and if so can anybody point me in the right
direction or to a doc that I can read that will help me to achieve this?


Note this section of the documentation:

https://www.bestpractical.com/docs/rt/latest/customizing/approvals.html#Approvers

Where it says:

Requestors: {$Tickets{TOP}->RequestorAddresses}

The content in the brackets is perl code. And it also talks about 
different ways you can assign to people or notify different groups.


So combining that, you can put some code in for the AdminCcGroup: value 
(or whatever would fit your workflow) to programmatically determine who 
to send the approval to:


AdminCcGroup: { $Tickets{TOP}->FirstCustomFieldValue('ApprovalGroup') }

Regards,

Re: [rt-users] New ticket layout change

[Parish, Brent]

I suspect the JavaScript answer is probably the cleanest and most flexible way.

In our environment, I have a number of departments that have all asked for 
their own (small) customizations for the SelfService Create Ticket page.

First I copied the CreateTicketInQueue.html page into local/html/SelfService.
Then I made a simple change to it:  An 'if' statement that checks for the 
presence of an HTML file in the same SelfService directory, matching the queue 
name.
If that HTML file is found, it will load that HTML file instead of the default 
'Create.html' file.
For example, If I have a queue named "Helpdesk" and a 
local/html/SelfService/Helpdesk.html file is found, RT loads that one.
 
--- CreateTicketInQueue.html.orig   2015-06-19 22:46:35.970131253 -0400
+++ CreateTicketInQueue.html2015-05-15 12:33:16.802273062 -0400
@@ -2,7 +2,7 @@
 %#
 %# COPYRIGHT:
 %#
-%# This software is Copyright (c) 1996-2015 Best Practical Solutions, LLC
+%# This software is Copyright (c) 1996-2014 Best Practical Solutions, LLC
 %#  
 %#
 %# (Except where explicitly superseded by other copyright notices)
@@ -47,16 +47,21 @@
 %# END BPS TAGGED BLOCK }}}
 <& Elements/Header, Title => loc("Create a ticket") &>

-<&|/l&>Select a queue for your new ticket
+<&|/l&>Please select a queue (department) for your new ticket

-
+
 % while (my $queue = $queues->Next) {
 % next unless $queue->CurrentUserHasRight('CreateTicket');

-<%$queue->Name%>
-<%$queue->Description%>
+% my $QueueName = $queue->Name;
+% if (-e "/opt/rt4/local/html/SelfService/$QueueName.html") {
+<%$queue->Name%>
+% } else {
+<%$queue->Name%>
 % }
-
+<%$queue->Description%>
+% }
+
 <%init>
 my $queues = RT::Queues->new($session{'CurrentUser'});
 $queues->UnLimit;

Then within each of the queue name HTML files I customize which fields are 
available (Sometimes), change how they appear on the page, add 'help' text for 
some fields, etc.

- Brent




-Original Message-
From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Matt Zagrabelny
Sent: Friday, September 18, 2015 10:59 AM
To: Kobus Bensch
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] New ticket layout change

On Fri, Sep 18, 2015 at 5:27 AM, Kobus Bensch  
wrote:
> Hi
>
> I am in the process of creating an electronic change request system in RT.
> At the moment the layout is as follows:
>
> --
> ---
> |  Create new ticket |  Basics
> |  Requestor | Queue
> |  CC |  Status
> |  Admin CC  | Owner
> |  Subject |---
> |  Describe Issue  |Assets
> | |---
> | |Custom Fields
> | |CF1
> | |cf2
> | |cf3
> | |cf4
> | |cfr5
> | |cf6
> | |cf7
> | |etc
> --
> ---
> How do I move the Custom field section to the left and across the 
> whole page for this one queue if possible?

JavaScript.

I've not rearranged the page with JS, but I'd imagine it could be done. Good 
luck.

> How do I change the filed sizes for CF's on a per field basis?

JavaScript.

I have done quite a bit of work with CFs via JS and there is some overhead to 
pay to get initially setup due to the JS needing to use the 'id' of the 
element. I'd be happy to write up what I've done, but let me know if you're 
serious about the undertaking - it'll probably take 10 or 20 minutes to write 
it up.

Cheers,

-m

[rt-users] New ticket layout change

[Kobus Bensch]

Hi

I am in the process of creating an electronic change request system in 
RT. At the moment the layout is as follows:


-
|  Create new ticket |  Basics
|  Requestor | Queue
|  CC |  Status
|  Admin CC  | Owner
|  Subject |---
|  Describe Issue  |Assets
| |---
| |Custom Fields
| |CF1
| |cf2
| |cf3
| |cf4
| |cfr5
| |cf6
| |cf7
| |etc
-
How do I move the Custom field section to the left and across the whole 
page for this one queue if possible?

How do I change the filed sizes for CF's on a per field basis?

Thanks in advance.

Kobus
P.S. I have searched for the 2 queries. On the first found no answers.
The second there are multiple answers, but I could not get any of them 
to work on a per field basis. Maybe just missing something.




--


Trustpay Global Limited is an authorised Electronic Money Institution 
regulated by the Financial Conduct Authority registration number 900043. 
Company No 07427913 Registered in England and Wales with registered address 
130 Wood Street, London, EC2V 6DL, United Kingdom.


For further details please visit our website at www.trustpayglobal.com.

The information in this email and any attachments are confidential and 
remain the property of Trustpay Global Ltd unless agreed by contract. It is 
intended solely for the person to whom or the entity to which it is 
addressed. If you are not the intended recipient you may not use, disclose, 
copy, distribute, print or rely on the content of this email or its 
attachments. If this email has been received by you in error please advise 
the sender and delete the email from your system. Trustpay Global Ltd does 
not accept any liability for any personal view expressed in this message.

Re: [rt-users] New ticket layout change

[Matt Zagrabelny]

On Fri, Sep 18, 2015 at 5:27 AM, Kobus Bensch
 wrote:
> Hi
>
> I am in the process of creating an electronic change request system in RT.
> At the moment the layout is as follows:
>
> -
> |  Create new ticket |  Basics
> |  Requestor | Queue
> |  CC |  Status
> |  Admin CC  | Owner
> |  Subject |---
> |  Describe Issue  |Assets
> | |---
> | |Custom Fields
> | |CF1
> | |cf2
> | |cf3
> | |cf4
> | |cfr5
> | |cf6
> | |cf7
> | |etc
> -
> How do I move the Custom field section to the left and across the whole page
> for this one queue if possible?

JavaScript.

I've not rearranged the page with JS, but I'd imagine it could be
done. Good luck.

> How do I change the filed sizes for CF's on a per field basis?

JavaScript.

I have done quite a bit of work with CFs via JS and there is some
overhead to pay to get initially setup due to the JS needing to use
the 'id' of the element. I'd be happy to write up what I've done, but
let me know if you're serious about the undertaking - it'll probably
take 10 or 20 minutes to write it up.

Cheers,

-m

Re: [rt-users] Migration from MySQL to PostreSQL - corrupt characters (german umlaut)

[Todd Wade]

On 9/17/15 8:12 AM, Maik Nergert wrote:

Hexcode from ü → c3 bc
is encoded again to → c3 83 (Ã) and c2 bc (¼)
(http://www.utf8-zeichentabelle.de/)


First I've upgraded RT from 3.8 to 4.2 with mysql db (utf8) and
everything went smoothly.


Can you confirm that the umlaut can be sucessfully added to the database 
after the upgrade but before the postgres migration?


I'm trying to determine if the issue happened during the upgrade or 
because of rt-serializer.