Re: [rt-users] Priority value
This extension may be what you're looking for -- https://metacpan.org/pod/RT::Extension::PriorityAsString It'll use configured (from RT_SiteConfig.pm) strings to represent numeric values. Aaron > On Jul 14, 2015, at 5:57 PM, ripa...@gmail.com wrote: > > Hi, > is there a way i can change the priority field in a ticket to a pull down > menu with 4 options like : > 100 - urgent 75 - high, and so on? > > Or use a custom field which the user selects, when the ticket is created > update the priorty numeric value? > > Thanks in advanced. > > Richard > > -- > Richard Pacheco >
Re: [rt-users] Question about pgp headers using GnuPG Inline option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 14 Jul 2015 22:51:55 -0500 Mario Góngora wrote: > I am trying to implement GnuPG on my RT (version 4.2.10) with the > Inline option, but when I send a message people are receiving this > type of wrapping : Can you show your %Crypt, %GnuPG and %GnuPGOptions settings? What version of GPG does `gpg --version` say you're running? - Alex -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlWl4ZEACgkQMflWJZZAbqBi1gCdHYg/6/ZAbfv2a1DyCDggmJYY MPYAn1Hz3vr0JA4LUhJ4m2ckFC3QSXc2 =/E5T -END PGP SIGNATURE-
Re: [rt-users] Priority value
On Tue, 14 Jul 2015 20:57:19 -0400 wrote: > Hi, > is there a way i can change the priority field in a ticket to a pull > down menu with 4 options like : > 100 - urgent 75 - high, and so on? > > Or use a custom field which the user selects, when the ticket is > created update the priorty numeric value? > > Thanks in advanced. Try https://metacpan.org/pod/RT::Extension::PriorityAsString - Alex
[rt-users] Question about pgp headers using GnuPG Inline option
Hello, I am trying to implement GnuPG on my RT (version 4.2.10) with the Inline option, but when I send a message people are receiving this type of wrapping : -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 my message -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJVpc9kAAoJEJ2MEvV/kJGBs6kH/iPSHRLOcXXYwz+tXqp4QmOL pHmS1yPnAOTluanYul4Mromo6LIQNAHk6FdGPXDMBBBWf/0+GaeNW3q8ap6GKble +r8pGuygb4fJAlMT4kjDSXVW+b2KeS3dSlSkRKOxnjiQiMfP7ISQ3zXtGYCGI2ix d0HzRkQ/01qpqKA716CU+G6ft6drtdIDsRqHAg5r9TaEF0bw5lBrUhj4zaaYhAus a/g+53JdtRqPZ4m7Ve0NT+409I+wxgWJQT74pR9YyYA8hYTh2kbcBKXlCh8BwGMt SwXgJ4OnBYLJzbmnnXUGaCO/7bsya5aJqyL0d5sSwAxMeOukRY2LSWdVfgZMWuI= =C+re -END PGP SIGNATURE- instead of something like -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I vote YES on this important measure. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: See Alan's GPG guide at https://futureboy.us/pgp.html iQIcBAEBCAAGBQJT3MFeAAoJEF8rR1bthz0jslMP/RMRODVKLmLwZ3sMR62COGc/ 0yQSh3c37qkkVjD0RvgdziHuCSSYelhNl7UMQofpdLonnJgPW3svlftE3Gn11JLp ZYv2iMwCzwyM2eLYpSQoJBNnGZzQDGnZRBkFOwdkkohUSBjhPjiszYw3KwnpsuxG I+m81IMJATR0wOylLumVdjbvS1/f9bOzBRvhgu2HS54lfPnl162RRZpycrrb5IOi 07QWIlUGVUdAxFUq4Jlm99KB17lQhri3zm6m7O5k0faD3IKFRTQGKseq7j88pRs6 j85v/cc35CHW9+66jcz7Y3UtOIj3gqDQd/Wj05YP01QSwSCuuVAezvXngljF8fLP OKQhFpLoLnWvDPgX3nKwGbX52qZwLGN0bZduhOmMPYwKAEFAYDOOW7q+i/dyz5xT od54j32QiNkSqDCVkvOT6dKiCdCa8GvtwwXPKa9X7+VZB2xYeJorJiaIesD7wyVN CQDx11uMGMkpZ/BmCIA5mDIkDnUTIxHxNFpn2kS6nHJqmJ/LleTpAKLhPWuY1U28 YVraBzmAZ/Wj2Frq0utPi4cFf5r3x9jXIzie4fYrUjMKCN+CNfLL15Py/z9OY1ux vvYdMiLAzL1Ujvjpyw7sCdc2KnbXaM9jmbBGjmVCMX/wGcGKT6cIxYnkR4NOW62L jaBgelaHIL5kZ+E/kpS6 =wh+e -END PGP SIGNATURE- do you have any idea, why is it wrapping the pgp headers that way? Best regards, Mario
[rt-users] Priority value
Hi, is there a way i can change the priority field in a ticket to a pull down menu with 4 options like : 100 - urgent 75 - high, and so on? Or use a custom field which the user selects, when the ticket is created update the priorty numeric value? Thanks in advanced. Richard -- Richard Pacheco
[rt-users] checking/changing default queue for a user
Hello listmates, If I as an admin need to set a certain queue for requests originating from a user - how do I do that? Let us say I have a user John Smith, with an email of jsm...@abc.com. How do I make it so that every ticket by email coming from jsm...@abc.com goes into a certain queue. Thanks. Boris.
Re: [rt-users] Weird behavior behind a proxy
Hi Bret, That should be Redirect permanent / https://proxy.damascusgrp.com/ Best Regards Martin On 2015-07-14 18:40, Martin Wheldon wrote: Hi Bret, It looks like you are missing a redirect/rewrite configuration on the proxy to map requests from http to https. Something like the following would be required on the proxy, obviously if the client can access the real RT server this won't work ServerName rt.damascusgrp.com Redirect permanent / https://rt.damascusgrp.com/ Best Regards Martin On 2015-07-14 17:48, Bret Wortman wrote: I've got a need to share a functioning rt instance behind a proxy, and for the most part, everything is working fine. But after actions taken through the proxy, the resulting URLs are always pointing to the original host name, not the proxy. On the proxy, we have the following: ProxyPass /rt/ http://rt.damascusgrp.com:80/rt/ [1] ProxyPassReverse /rt/ http://rt.damascusgrp.com:80/rt/ [1] Our users can then access the system okay at https://proxy.damascusgrp.com/rt/ [2]. But after they login, they're directed to http://rt.damascusgrp.com/rt/ [3]. Likewise, after switching back to the correct URL, after creating or updating a ticket, they are directed to http://rt.damascusgrp.com/rt/Ticket/Display.html. [4].. What have I missed? I'm by no stretch an expert at either RT or Apache proxy configuration. Thanks, Bret Wortman Links: -- [1] http://rt.damascusgrp.com:80/rt/ [2] https://proxy.damascusgrp.com/rt/ [3] http://rt.damascusgrp.com/rt/ [4] http://rt.damascusgrp.com/rt/Ticket/Display.html. !DSPAM:41,55a549b5136401427644005!
Re: [rt-users] Weird behavior behind a proxy
Hi Bret, It looks like you are missing a redirect/rewrite configuration on the proxy to map requests from http to https. Something like the following would be required on the proxy, obviously if the client can access the real RT server this won't work ServerName rt.damascusgrp.com Redirect permanent / https://rt.damascusgrp.com/ Best Regards Martin On 2015-07-14 17:48, Bret Wortman wrote: I've got a need to share a functioning rt instance behind a proxy, and for the most part, everything is working fine. But after actions taken through the proxy, the resulting URLs are always pointing to the original host name, not the proxy. On the proxy, we have the following: ProxyPass /rt/ http://rt.damascusgrp.com:80/rt/ [1] ProxyPassReverse /rt/ http://rt.damascusgrp.com:80/rt/ [1] Our users can then access the system okay at https://proxy.damascusgrp.com/rt/ [2]. But after they login, they're directed to http://rt.damascusgrp.com/rt/ [3]. Likewise, after switching back to the correct URL, after creating or updating a ticket, they are directed to http://rt.damascusgrp.com/rt/Ticket/Display.html. [4].. What have I missed? I'm by no stretch an expert at either RT or Apache proxy configuration. Thanks, Bret Wortman !DSPAM:41,55a53cad136401860415760! Links: -- [1] http://rt.damascusgrp.com:80/rt/ [2] https://proxy.damascusgrp.com/rt/ [3] http://rt.damascusgrp.com/rt/ [4] http://rt.damascusgrp.com/rt/Ticket/Display.html.
Re: [rt-users] [rt-devel] Need help
On Tue, Jul 14, 2015 at 11:50 AM, Guiguemde Jacques Rodrigue wrote: > Ok cool > Thank u for this information, > But i tried to follow the instructions given but he did not even offer > me suggestions when I entered. How to suggestion when I keyboarding? Hi, I didn't really give any instructions, just advice and some documentation links. I'm unable to understand what you are asking. :/ -m
[rt-users] Weird behavior behind a proxy
I've got a need to share a functioning rt instance behind a proxy, and for the most part, everything is working fine. But after actions taken through the proxy, the resulting URLs are always pointing to the original host name, not the proxy. On the proxy, we have the following: ProxyPass /rt/ http://rt.damascusgrp.com:80/rt/ ProxyPassReverse/rt/http://rt.damascusgrp.com:80/rt/ Our users can then access the system okay at https://proxy.damascusgrp.com/rt/. But after they login, they're directed to http://rt.damascusgrp.com/rt/. Likewise, after switching back to the correct URL, after creating or updating a ticket, they are directed to http://rt.damascusgrp.com/rt/Ticket/Display.html... What have I missed? I'm by no stretch an expert at either RT or Apache proxy configuration. Thanks, *Bret Wortman*
Re: [rt-users] [rt-devel] Need help
Hello, This question is better suited for rt-users. I've tweaked the reply above to move it over. On Tue, Jul 14, 2015 at 9:55 AM, Guiguemde Jacques Rodrigue wrote: > Hello, > In my manipulations I activated an option that transforms the field > involved in the creation of a ticket. This field initially > a dropdown. But now he becomes textbox field with the default value > Nobody. Okay. > I'd really like to reaffirm this combo. It could have happened due to the number of users who have the OwnTicket right granted to them. If the number of users with that right exceed 50, then RT automatically makes the input an autocomplete instead of drop down. https://www.bestpractical.com/docs/rt/4.2/RT_Config.html#AutocompleteOwners If you really want to always force a drop down and you have more than 50 users with OwnTicket right, then you can create your own callback: from share/html/Elements/SelectOwnerDropdown my $dropdown_limit = 50; $m->callback( CallbackName => 'ModifyDropdownLimit', DropdownLimit => \$dropdown_limit ); and set it to something big. -m
