[rt-users] [rt-announce] RTIR 3.0.3 Released

RTIR 3.0.3 contains a number of bug fixes since 3.0.2 We noticed that the upgrade script from 2.6-3.0 removed all of the RTIR specific SLA Scrips but failed to account for the SLA Custom Field. This would cause confusion if you installed RT::Extension::SLA and tried to use it with two SLA fields.

[rt-users] Continued Migrations Questions -

On my continued migration from ZenDesk I've come across something that honestly I've not done with RT. Templates, Queues and app configuration, I feel good with. Something unique to my current workplace is the need for multiple domains email addresses. I know I can catch this downstream in a

[rt-users] Not receiving alerts when requester responds to h...@support.domain.com

This system has been in place and setup by another user previously, however, when a requester responds to just h...@support.domain.com the ticket owner or the tech responding to the ticket does not get any email alerts of replies directly to that ticket from a requester. So I'll respond to a

[rt-users] Using an asset custom field as the asset id

When using the asset csv import extension you can configure it to use one of the column names as the id of the created asset. What i don't see is a way to do this when creating an asset through the website. This means that potentially i will get issues if i create assets manually and then import

Re: [rt-users] Auto Resolve Aged Tickets - Custom Email Template

Thanks, but I don't think this is what we are looking for. Here is what we are looking for: - If we manually resolve a ticket, this should send out one email template - If there is an aged ticket, we want it to auto resolve, and then send out a different custom template (I can get the tickets

Re: [rt-users] Auto Resolve Aged Tickets - Custom Email Template

On Wednesday, October 22, 2014, 3:21:05 PM, wrender wrote: Thanks, but I don't think this is what we are looking for. Here is what we are looking for: - If we manually resolve a ticket, this should send out one email template - If there is an aged ticket, we want it to auto resolve, and

[rt-users] rt-users] Continued Migrations Questions -

Hi Matt, Yes you can do this on a per queue basis. My term for this is per queue branding - I'm not sure if there's an official term for it. A disclaimer - there are probably better / more efficient ways of doing this; I'm not an expert but this is how we have it working. So in a nutshell... -