RT

Request Tracker

RT (Request Tracker) is the ticketing system the con uses to handle email requests. As of 2016, all departmental emails are handled in RT.

The best way to think of RT is like a really fancy group email system. Queues are the group email boxes. Multiple people can see and handle emails, and everyone who is involved with that box gets updated on everything going on so that everyone is on the same page.

Video Tutorials

Beta made a four-part video tutorial series, which is posted on our YouTube: https://www.youtube.com/playlist?list=PLnJMQShIVjsl4XuTJJ4bPEYWDJJowhEN0

Logging in

You can access RT from https://tickets.snafucon.com/. Your account is linked to BACON so log in with your current username and password. However, you will need to have privileges set up by the admin or you will only be able to see your previous tickets (if any) but not actually be able to see or answer any from the queue.

Setting your Signature

When logged in:

Hover over "Logged in as {you}"
Hover over Settings
Click "About Me"
Your signature box is on the lower left. Edit as you see fit.
Click "Save Preferences"

Signature Format

{Your Name}
{Your Title or Department, as relevant}
Sierra Nevada Anime Fans Unite!
https://snafucon.com
{Optional relevant message}

Example Signature

Beta
SNAFU Con Human Resources
Sierra Nevada Anime Fans Unite!
https://snafucon.com
Apply now! https://register.snafucon.com/staff/apply/

Queues

Most users will only have one Queue, but some users will have multiple ones. The easiest way to navigate RT is by queue. The Queues you have access to are listed on the right-hand side of the screen under "Quick Search."

Click on the queue name to see all the tickets in a queue.

Reply/Comment to a Ticket

When you reply to a ticket it is sent to all of the people who administer the queue that it is in, and the requester (the person who sent the email in the first place.)

When you comment on a ticket, it is only sent to the people who administer the queue.

There are two ways of replying to and commenting on tickets.

Reply by Email

You should only reply by email if you aren't closing or resolving the ticket. You can not resolve the ticket by email.

Simply respond to the email that was sent to you.

Notice that the email you're sending goes back to the queue email. So, if you're responding to an email that originally went to [email protected], then the email you send will also go to [email protected] It is important that you do not alter the [SNAFU #(number)] part of the subject. RT will look at the subject to put the reply in the right ticket.

The information that is added to the beginning of the email you received (the ticket information with Queue info and Ticket URL, etc.) WILL be included in your email if you don't delete it. It is up to you if you want that information in your email, but it should probably be removed before sending to minimize confusion.

Comment by Email

Comment by replying and changing the email to (queue email)[email protected] snafucon.com So if the queue email was registration, you can comment by sending an email to [email protected]

As before, keep the [SNAFU #(number)] part of subject the same so RT can route your comment correctly.

Reply/Comment by Logging In

To reply to a ticket you need to get into a ticket to view it. You can click on a ticket from your dashboard, or from your queue.

To reply/comment to the ticket, scroll down to the History section. You can view all history for this ticket (emails in and out).
Click Reply or Comment
If you are the first reply, on the right-hand side you may want to update the Status to Open and the Owner to you. RT should update it for you after your reply if you don't make any settings. If you are closing the ticket you will want to change the status to resolved (or rejected as applicable).
Type your reply in the box (if you have one set up, your signature is automatically added to the end of the message - if you are replying at the top of the message make sure your signature is at the top. If you are replying in-line, your signature stays at the bottom).
If you want to add a person as a one-time cc or bcc, then do that in the applicable fields
When you are ready to send your reply (or add your comment), click "Update Ticket" and your reply will be sent and will show in the ticket history

NOTE: The reply box is exactly the same for reply or comment except it will be pink if you are replying. If you want to change your reply to a comment (or vice versa) on the right-hand side of the screen there is a drop-down menu and you can change whether the message you are writing is a reply or a comment. The color of the text area will change accordingly.

Creating a Ticket/Emailing Out

Bulk Update

To do a bulk update (most useful for deleting spam):

From the landing page, click on the queue you want to update (right-hand side of the screen)
In the upper-right corner, click on Bulk Update
Uncheck the messages you want to leave alone, or use the Clear All button at the bottom if that's faster.
Once you have only the messages checked that you want to update, scroll to the bottom
In the form at the bottom make the changes that you want to apply to all the messages checked. To set them to "deleted," you pull down the drop-down next to Make Status and choose deleted.
Once you have filled the form with all the changes you want to make, click Update.

You can also use Bulk Update to merge tickets (see below) or do many other maintenance tasks. Deleting is the most common.

Updating a Ticket

Once you are in a ticket you will see a header with all sorts of information you can change. Every section had things you can modify by clicking on its header. So, if you want to update who owns the ticket and whether it's open/closed, you can click on The Basics and update those things from there. If you have multiple queues you can change what queue the ticket is in from The Basics section, because people often send requests to the wrong email.

Statuses

Initial Phase (search __initial__)

The ticket is new and hasn't yet been reviewed by department staff.

triage: The initial status for tickets created via email. These tickets are waiting for triage, and may be spam.
new: The ticket has been triaged and is not spam, but has not yet been reviewed by department staff.

Active Phase (search __active__)

The ticket has been reviewed by a staffer at least once and is actively being worked on.

review: Something has happened (usually a reply) and the ticket needs the attention of a staffer.
working: The ticket has been reviewed, but the Owner still needs to reply. This should only be set by the ticket owner, and indicates that they're working on a reply and so it doesn't need to be reviewed by anyone else.
waiting: We're waiting for the Requestor to reply. No action is needed.
timeout: The ticket was waiting, but the Requestor hasn't responded for too long. Either send a reminder or set to abandoned.
hold: No one needs to do anything, but we don't want the ticket to be closed for some reason.

Inactive Phase (search __inactive__)

The ticket does not require more work and should not normally be shown. Inactive tickets can still be found via the search system.

resolved: The Requestor's objective has been achieved and the ticket is closed.
rejected: We declined to do what the Requestor wanted and the ticket is closed.
abandoned: The Requestor took too long to respond and we gave up, so the ticket is closed.
deleted: The ticket isn't spam, but we want it to go away and there's no reason to keep it as a permanent record. This will be used most often for automated notifications from various systems. Tickets in the deleted status aren't actually deleted immediately: they stick around for at least 30 days before being shredded.
spam: The ticket is spam and should go away. Tickets marked spam will be kept for at least 30 days, then used to train the spam filter and shredded.

Merging Tickets

Sometimes the way someone replies to a thread opens a new ticket. Sometimes people email multiple times. Sometimes you just need to merge everything together.

If you have two or more tickets that are really all part of the same thread then they should be merged into the same ticket. Luckily, merging is really easy (a little TOO easy).

Merging One Ticket

In the ticket view click on "Links"
Fill out the Merge Into field the bottom
Click Save Changes

The ticket is now merged.

Merging by Bulk Update

The way you merge tickets is:

Determine the id number of the main ticket you want to merge into.
Go to bulk update for that queue and select the other ticket(s) you want to merge
Scroll to the bottom and enter the id number of the main ticket
Click Update.

You should now have the whole thread in one. Notice that it warns that the process is not reversible, so don't mess it up!

CAUTION: If you do any more bulk updating RT will continue to merge tickets until you either navigate to another page or clear out the merge field!

Forwarding a Ticket into RT

If an email went to the wrong place and you need to get it into RT you need to forward it there and update it so replies can be done correctly. Depending on the queue or the time, you may not have the ability to update it yourself, so you may have to warn the queue handlers to update the ticket for you.

Forward the email out of your email to the correct email
Go into RT and open the ticket that was just created. It will say that you're the requestor. If the queue handler replied now it would go to you, not the original requestor
In the ticket, scroll down to "People" and click the Edit icon
Click the checkbox next to your name/email to remove it as a requestor
Under "Add new watchers" pick one and use the drop-down to change it to "Requestor"
Add the original requestor's email to the email box next to where you just changed
Click Save
Review the people box to ensure you did it right - your email should be gone, and the original person who emailed you should be the requestor

For the Admin

Create a Privileged User

Admin->Users->Select
Put user in the go to user box.
- If the user does not exist, it needs to be created. So you can create the user by sending them an email from RT letting them know they can log into RT. It's freaking magic!
Open the user account
Check the box to make the user a privileged user
Save Changes at the bottom

Add a user to a queue

Admin->Queues->Select
Select the queue
Click "Watchers"
enter the user's name in the "Find People whose" box and hit Go - The user will show up in the lower right area
Select "AdminCC"
Click "Save Changes"

Merging users where the good email is on the account not connected to BACON

This is a common but really, really annoying condition where RT will will not email to the BACON email because the BACON account is already linked to a different email. It is common when people change their email address, though.

Beta's Method

I don't know if this is the best way but here's how I'm handling it on an old ticket and a way that Sammich seems to believe will work.

Copy good and bad emails to a third location like notepad so I have them safe for this process. I like to be very clear in my notes "good email: (email)" and "bad email:(email)" along with links to each user so if I messed up I had all the information still available.
On the bad account, set the email address (and possibly the username if it's the same as the email address) to something unique but bogus. I used "[email protected]" because the email in question was @gmail and it was temporary and easy.
On the good account, set the email address to what you want it to be: the "good" email address
Save
On the bad account, set the email address to what the good account use to have: the "bad" email address
Save
Merge the "bad" user into the "good" user

Sammich's Method/note

What I did is change the non-BACON-linked account with the new email to have no email, change the BACON-linked account to the correct email, and then merge the non-BACON account into the BACON account. If they're still going to use the old address you'd either need to swap the addresses as you said, or create a new account for the old email and immediately merge it into their main account.

RT

Contents