Re: [rt-users] Lockdown CC and AdminCC
On Mon, Aug 24, 2015 at 4:51 AM, Joseph D. Wagner j...@josephdwagner.info wrote: I need to limit what users can enter into CC and AdminCC. I cannot have them entering email addresses for those without logins. What do you mean by without logins? The email address needs to correspond to a user that already exists on the system? -m
Re: [rt-users] multiple customers in one RT instance?
On Mon, Aug 24, 2015 at 6:01 AM, lu...@sulweb.org wrote: Hello, I'm new to RT and I provide my customers managed hosting for their websites, email and other web applications. I'd like to offer my customers a product like one RT queue each, preconfigured to work with the required email addresses at the customer internet domain. Each RT queue doesn't need any customization. I need each customer to see only his queue. I've read http://requesttracker.wikia.com/wiki/MultipleInstances but I'd prefer to avoid multiple RT instances, even if they shared a common base. I think I don't really need multiple instances and I suspect I can go with just groups and permissions, one group for each customer, however I'm not totally sure that's a viable solution. Is it possible to isolate each customer on his queue using a single RT instance? Try: User is privileged User has SeeQueue right granted for their queue Give other rights as needed. -m
Re: [rt-users] Lockdown CC and AdminCC
What do you mean by without logins? The email address needs to correspond to a user that already exists on the system? Yes. Here's what happened. A privileged user entered an external email address into the CC field, which did not have an account. RT autocreated an account for that person, and it accepted that external email address on the CC field. I need to prevent that. How can I limit CC and AdminCC to email addresses that already have accounts? Either rejecting the ticket or silently failing to add the CC/AdminCC email address would be acceptable. Joseph D. Wagner
Re: [rt-users] Problem with extension RepeatTicket
are there any other informations which i could share with you that might help for solving the issue ? Regards, Dave -- View this message in context: http://requesttracker.8502.n7.nabble.com/Problem-with-extension-RepeatTicket-tp60471p60502.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
[rt-users] Lockdown CC and AdminCC
I need to limit what users can enter into CC and AdminCC. I cannot have them entering email addresses for those without logins. How can I limit or secure this? Joseph D. Wagner
Re: [rt-users] Quick Search
[cid:image001.jpg@01D0DE54.0E4E0E40] Thanks for the reply, I am using the searches that RT generates (see screen shot) when you are watching a queue. Is there any way to edit these? Thanks Sam From: Zoey Schutt [mailto:z...@braincoral.io] Sent: 19 August 2015 18:37 To: Sam Maher Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Quick Search Greetings, You can change the order in which the tickets show up for the quick search by editing the search, then modifying the Sorting section. By default you will see that the search is being sorted by ID, Asc. I have attached a screenshot of what it will look like. You will want to change this to ID, Desc which will show the newest tickets first. -- Zoey Schutt Braincoral Technology On Mon, 17 Aug 2015 10:10:47 -0400 Sam Maher sam.ma...@lawsonlewisblakers.co.ukmailto:sam.ma...@lawsonlewisblakers.co.uk wrote Hi, We have quick search on our users dashboards so they can click on the queue and view the tickets that are in the queue they clicked on. The only problem is that it shows the oldest tickets first not the newest ones. Is there any way that we can change this? Thanks Sam Sam Maher - IT Technician Lawson Lewis Blakers T: 01323 720142 F: 01323 725349 Partners: Jeremy H Sogno, Nadine M Ashford and Mark Barrett Lawson Lewis Blakers Solicitors Authorised and Regulated by the Solicitors Regulation Authority. SRA No: 00053703 THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE LEGALLY PRIVILEGED If you are not the addressee or the intended recipient any disclosure, copying, distribution, or other use of this e-mail and attachments is strictly prohibited. If you have received this e-mail in error please notify the sender immediately and delete this e-mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, be incomplete or contain viruses. We do not accept liability for any errors or omissions which arise as a result of e-mail transmission. Any e-mail attachment may contain software viruses. Whilst reasonable precaution has been taken to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. Lawson Lewis Blakers reserves the right to monitor or record e-mails for any purpose allowed by prevailing legislation. Sam Maher - IT Technician Lawson Lewis Blakers T: 01323 720142 F: 01323 725349 Partners: Jeremy H Sogno, Nadine M Ashford and Mark Barrett Lawson Lewis Blakers Solicitors Authorised and Regulated by the Solicitors Regulation Authority. SRA No: 00053703 THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE LEGALLY PRIVILEGED If you are not the addressee or the intended recipient any disclosure, copying, distribution, or other use of this e-mail and attachments is strictly prohibited. If you have received this e-mail in error please notify the sender immediately and delete this e-mail. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, be incomplete or contain viruses. We do not accept liability for any errors or omissions which arise as a result of e-mail transmission. Any e-mail attachment may contain software viruses. Whilst reasonable precaution has been taken to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. Lawson Lewis Blakers reserves the right to monitor or record e-mails for any purpose allowed by prevailing legislation.
Re: [rt-users] Problem with extension RepeatTicket
Excuse the delay in my response - I was not at work on Friday. After reading your comments I re-examined my settings for RepeatTicket and it turns out I was incorrect about my cronjob - Repeated tickets were not being created how I expected. I have now made four separate cronjobs as a temporary work-around until I find out why the Ticket Recurrence settings are not working as expected. Here they are: 1. 30 08 * * * /usr/local/share/request-tracker4/plugins/RT-Extension-RepeatTicket/bin/rt-repeat-ticket --type daily - Fires at 8:30am daily. 2. 30 08 * * 1 /usr/local/share/request-tracker4/plugins/RT-Extension-RepeatTicket/bin/rt-repeat-ticket --type weekly - Fires at 8:30am on Monday of every week. 3. 30 08 1 * * /usr/local/share/request-tracker4/plugins/RT-Extension-RepeatTicket/bin/rt-repeat-ticket --type monthly - Fires at 8:30am on the first day of every month. 4. 30 08 1 1 * /usr/local/share/request-tracker4/plugins/RT-Extension-RepeatTicket/bin/rt-repeat-ticket --type yearly - Fires at 8:30am on the first month of every year. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Problem-with-extension-RepeatTicket-tp60471p60504.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
Re: [rt-users] Lockdown CC and AdminCC
On Mon, Aug 24, 2015 at 2:02 PM, Joseph D. Wagner j...@josephdwagner.info wrote: What do you mean by without logins? The email address needs to correspond to a user that already exists on the system? Yes. Here's what happened. A privileged user entered an external email address into the CC field, which did not have an account. RT autocreated an account for that person, and it accepted that external email address on the CC field. I need to prevent that. How can I limit CC and AdminCC to email addresses that already have accounts? Either rejecting the ticket or silently failing to add the CC/AdminCC email address would be acceptable. Use a callback. Do you know what those are? -m
Re: [rt-users] Lockdown CC and AdminCC
On 24 Aug 2015, at 15:40, Matt Zagrabelny wrote: On Mon, Aug 24, 2015 at 2:02 PM, Joseph D. Wagner j...@josephdwagner.info wrote: What do you mean by without logins? The email address needs to correspond to a user that already exists on the system? Yes. Here's what happened. A privileged user entered an external email address into the CC field, which did not have an account. RT autocreated an account for that person, and it accepted that external email address on the CC field. I need to prevent that. How can I limit CC and AdminCC to email addresses that already have accounts? Either rejecting the ticket or silently failing to add the CC/AdminCC email address would be acceptable. Use a callback. Do you know what those are? Specifically: You can use the BeforeCreate callback to prevent accidental creation of . It is available in Ticket/Create.html, SelfService/Create.html, and m/ticket/create. It is NOT available for the QuickCreate widget, so users of that widget could add bogus Requestors at will. Anyone who can add ad hoc recipients to ticket updates share the ability to add users to RT, so you may want to find a callback in the Update pages as well. If controlling user creation by gatekeeping many different paths of ticket modification seems like a shoddy approach to you, you are not wrong. In RT's defense, its eagerness to add new users whenever it sees a new email address is rooted in the days before spam from random addresses to random addresses and via random compromised web applications was a widespread problem. If you use ExternalAuth, setting AutoCreateNonExternalUsers to 0 seems to be an option that would block creation of users not in one of your configured external auth sources, but it may have undesirable side-effects. If you want random strangers to be able to send your RT mail that opens new tickets, you are stuck with gatekeeping other paths to user auto-creation.
[rt-users] REST API - How to set the content type to text/html
I am currently creating tickets and commenting on tickets using the CLI. I am
able to define what the content type is ('text/html'). I do not see a way to
define the content type using the REST API. Is there a way to define what the
text type will be? I am using the latest version of RT.
Thanks in advance.
