Difference between revisions of "ManualUsingWebInterface"

From Request Tracker Wiki
Jump to navigation Jump to search
m (18 revisions imported)
m
 
(58 intermediate revisions by 2 users not shown)
Line 9: Line 9:
If you see any unfamiliar terms in this chapter, look for them in the RT Concepts section of [[ManualIntroduction]], or in [[RTGlossary]].
If you see any unfamiliar terms in this chapter, look for them in the RT Concepts section of [[ManualIntroduction]], or in [[RTGlossary]].


This manual is being updated to 3.8; we're going to snip out references to things that were markedly different in older -- particularly pre-3.x -- releases. If you have one of those... you '''really''' need to think about upgrading.
This manual is being updated to 4.4; we're going to snip out references to things that were markedly different in older -- particularly pre-4.x -- releases. If you have one of those... you '''really''' need to think about upgrading.


= Logging In =
= Logging In =
Line 15: Line 15:
Your administrator will tell you where your login page is, and what username and (usually) temporary password to use. The login screen looks like this:
Your administrator will tell you where your login page is, and what username and (usually) temporary password to use. The login screen looks like this:


[[File:RT-Login.png|frame|RT Login]]
[[File:RT-Login.png|RT Login Page|thumb|500px]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


Type your username in the Username text box, type your password in the Password text box, and then click the Login button, or hit ENTER.


Type your username in the Username text box, type your password in the Password text box, and then click the Login button, or hit ENTER.
= RT at a Glance (Home Page) =


= Home Page =
Immediately after logging in, you'll be looking at the home page, RT at a Glance.


Immediately after logging in, you'll be looking at the home page: ''screenshot needed.''
[[File:RT-at-a-Glance.png|RT at a Glance|thumb|500px]]


'''NOTE:''' You'll find that many items are clickable hotlinks in the RT interface, such as ticket numbers and queues, but the default interface configuration does not highlight these using the usual blue color or underline. Move your mouse around; things which are links will get an underline when you hover the mouse over them. Clicking on these items takes you pretty much where you might expect it would.
'''NOTE:''' You'll find that many items are clickable hotlinks in the RT interface, such as ticket ids and queues, but the default interface configuration does not highlight these using the usual blue color or underline. Move your mouse around; things which are links will get an underline when you hover the mouse over them. Clicking on these items takes you pretty much where you might expect it would.


Also, note that your installation may have been customized by the administrator, and because of that, things may be in different places than we describe here.
Also, note that your installation may have been customized by the administrator, and because of that, things may be in different places than we describe here.


= RT AT A GLANCE =
The main part of the page, called "RT at a Glance", will contain a collection of panels, each of which can be minimized, and some of which can also be edited.
 
Let's start with the center section of the page on the white background. This main part of the page, called "RT at a Glance", will contain a collection of panels, each of which can be minimized, and some of which can also be edited.


By default, these are:
By default, these are:
Line 69: Line 35:
== In the left column ==
== In the left column ==


* 10 highest priority tickets I own: This section displays what you need to do. Each ticket will display its number, subject, queue, and status from this page. Click any ticket's number or description to display its basic information page (see also the Tickets interface section of this chapter).
* 10 highest priority tickets I own: This section displays what you need to do. Each ticket will display its id, subject, queue, and status from this page. Click any ticket's id or description to display its basic information page (see also the [[ManualUsingWebInterface#Tickets_interface|Tickets interface]] section of this chapter).
* 10 newest unowned tickets: Here you'll see the list of tickets which have been created, but not yet assigned to anyone, sorted with the newest ones at the top. Each ticket has an associated '''Take''' link which you can use to assign the ownership of the ticket to yourself, and start working on it.
* 10 newest unowned tickets: Here you'll see the list of tickets which have been created, but not yet assigned to anyone, sorted with the newest ones at the top. Each ticket has an associated '''Take''' link which you can use to assign the ownership of the ticket to yourself, and start working on it.
* Bookmarked tickets: New in 3.8 (CHECKME) is a facility where you can bookmark any ticket while you're looking at it, no matter its queue or owner, by clicking on an empty star (like the [http://www.mozilla.org/en-US/firefox/new/ Mozilla Firefox] 3 bookmark star) in the top right corner of the page. Tickets you've bookmarked in this way will be displayed in this panel.
* Bookmarked tickets: Here is a facility where you can bookmark any ticket while you're looking at it, no matter its queue or owner, by clicking on an empty star in the top right corner of the page. Tickets you've bookmarked in this way will be displayed in this panel.
* Quick Ticket Creation: This panel lets you enter the bare minimum of information about a new ticket, to create one quickly when necessary. If you need to enter more information about a new ticket, including things like [[CCs]], select a queue from the top 'eyebrow' bar of the page, and click the "New Ticket In" button; this will give you the complete New Ticket screen.
* Quick Ticket Creation: This panel lets you enter the bare minimum of information about a new ticket, to create one quickly when necessary. If you need to enter more information about a new ticket, including things like [[CCs]], select a queue from the top submenu of the page, and click the "New Ticket In" button; this will give you the complete New Ticket screen.


== In the right column ==
== In the right column ==


* Reminder - New in 3.8, if you have set a reminder for yourself in a ticket. You will see the title of the reminder and which ticket it belongs to. Click on the Title of the reminder to follow it.
* My Reminders - If you have set a reminder for yourself in a ticket, you will see the title of the reminder and which ticket it belongs to. Click on the title of the reminder to follow it.
* Quick search: This panel contains a list of all the queues you're permitted to access, logged in as the user you are. They're in alphabetical order, and show the number of New, Open and Stalled tickets.
* Queue List - This panel contains a list of all the queues you're permitted to access, logged in with the current user account. They're in alphabetical order, and show tickets in each status based on the queue lifecycle.
* Dashboards: The Dashboards panel (see [[ManualDashboards]]) will contain a list of any Dashboards which have been created for the entire RT installation, your user group, or your personally created dashboards.
* Dashboards: The Dashboards panel (see [[ManualDashboards]]) will contain a list of any Dashboards which have been created for the entire RT installation, your user group, or your personally created dashboards.
* Refresh: This pulldown menu, on the lower right side of the screen, lets you select whether the homepage is automatically refreshed or not. The default is no. Other options are refreshing the page every 2, 5, 10, 20, 60, and 120 minutes. Click the Go! button to select the displayed auto-refresh delay.
* Refresh: This pulldown menu, on the lower right side of the screen, lets you select whether the homepage is automatically refreshed or not. The default is no. Other options are refreshing the page every 2, 5, 10, 20, 60, and 120 minutes. Click the Go! button to select the displayed auto-refresh delay.
Line 83: Line 49:
== Top navigation bar ==
== Top navigation bar ==


* New ticket in: Use this to quickly start creating a ticket (for more detail, see the Creating a new ticket section in this chapter). Choose a queue from the drop-down menu and click the "New ticket in:" button to begin.
This is the RT main menu. The options will expand into a menu tree as you select various tasks. Your current location in this tree will always be boldfaced. Some of these options may not be displayed if you do not have the appropriate rights.
* Search: type a search term in the text box and click the Search button to find tickets. This box can do some magic, for example you can type in a ticket number, and jump directly to that ticket. Check out [[ManualSimpleSearch]] for more on the magic and [[ManualSearchTickets]] for more ways to search tickets.
* Preferences: click this link to edit your personal information on RT. On a basic level, this is information such as email address, name, password, phone numbers, location, and signature. This is also where you start working with personal groups and delegating rights, features which we'll explain later in this chapter. This link will not appear if you have not been granted the [[ModifySelf]] right.
* Logout: click this to log out of RT. You can leave yourself logged into RT without breaking anything, but logging out is a good habit to get into for security purposes.


= Left side navigation bar =
* Home: the home page: where you are now. You can always get back to the home page by clicking Home in the upper left of the screen. You can even click this if you're '''on''' the home page, as an easy Refresh link.
* Search: clicking this brings you to the ticket search query builder page (see also [[ManualUsingWebInterface#Searching_for_tickets|Searching for tickets]]).
* Reports: This allows you to quickly create reports on tickets Resolved by owner, Resolved in date range or Created in a date range.
* Articles: clicking this takes you to Articles, RT's integrated knowledgebase.
* Assets: Assets allow you to keep an inventory of items that can then be linked to tickets as needed
* Tools: The options here allow you to view your daily progress, check your reminder and view any approvals you may need
* Admin: This link takes administrators to the section of RT where they can configure users, queues and scrips, and make global setup changes to the installation.
* Logged in as: This menu lets you configure RT for your personal tastes. You can also log out of RT here.


This is the RT main menu. The options will expand into a menu tree as you select various tasks. Your current location in this tree will always be boldfaced. Some of these options may not be displayed if you do not have the appropriate rights.
== Top submenu ==


* Home: the home page: where you are now. You can always get back to the home page by clicking Home in the upper left of the screen. You can even click this if you're '''on''' the home page, as an easy Refresh link.
* New ticket in: Use this to quickly start creating a ticket (for more detail, see [[ManualUsingWebInterface#Creating_a_new_ticket|Creating a new ticket]]). Choose a queue from the drop-down menu and click the "New ticket in:" button to begin.
* Tickets: clicking this brings you to the ticket search page (see also the 'Common tasks: Searching' section of this chapter).
* Search: Type a search term in the text box and click the Search button to find tickets. This box can do some magic, for example you can type in a ticket id, and jump directly to that ticket. Check out [[ManualSimpleSearch]] for more on the magic and [[ManualSearchTickets]] for more ways to search tickets.
* Tools: the Tools menu lets you configure RT for your personal tastes.
* RTFM: clicking this takes you to RTFM, RT's integrated knowledgebase, if it's installed. (documented separately).
* Configuration: This link takes administrators to the section of RT where they can configure users, queues and scrips, and make global setup changes to the installation.
* Approval: sometimes, a ticket may require the approval of someone in your organization before it can be resolved. This section shows the status (pending, approved, denied) of approval requests. Most users won't need to worry much about Approvals; there is more detail in [[ManualAdministration]].


= Tickets interface =
= Tickets interface =
Line 106: Line 72:


* from the Home page, click a ticket subject under '''10 highest priority tickets I own''' or '''10 newest unowned tickets'''. Or, you can '''Take''' an unowned ticket, which has the extra side effect of assigning ownership to you.
* from the Home page, click a ticket subject under '''10 highest priority tickets I own''' or '''10 newest unowned tickets'''. Or, you can '''Take''' an unowned ticket, which has the extra side effect of assigning ownership to you.
* search for a ticket, from the search box on the Home page or by clicking Tickets in the left side navigation bar. Then click the ticket.
* search for a ticket, from the search box on the Home page or by clicking Search in the top navigation bar, then click on the ticket.
* click a queue name on the Quick Search panel and then click a ticket.
* click a queue name on the Queue List panel and then click a ticket.
* clicking a ticket's URL from within an email message.
* clicking a ticket's URL from within an email message.


Line 114: Line 80:
Any way you navigate to a ticket, you'll arrive at that ticket's Display page first.
Any way you navigate to a ticket, you'll arrive at that ticket's Display page first.


The Display view, the first of 8 possible views of the ticket, (pictured above) provides an overview of the ticket.
The Display view, the first of many possible views of the ticket, (see screenshot) provides an overview of the ticket.
 
[[File:Ticket-Display.png|Ticket Display Page|thumb|500px]]


Two panes come up on the Display view: Ticket Metadata on top, and History below.
Two panes come up on the Display view: Ticket Metadata on top, and History below.


As you can see, it includes information like Basics, People, Reminders, Dates, and Links, each in it's own sub-pane.
As you can see, it includes information like Basics, People, Reminders, Dates, and Links, each in it's own portlet.


The number and title of the ticket it above the top command bar, and the number is also in the left-side menu, in bold. If you picked the ticket out of a list, then that menu will also contain navigation links to move around that list, First, Prev, Next, and Last.
The id and subject of the ticket is above the top command bar.


In the upper right corner of the main window, ticket pages will generally offer (some of) the options Reply, Resolve, Open, Take, Comment, and Extract Article. Reply and Comment will be covered shortly, in the Replying and Commenting section of this chapter. Resolve means to close a ticket because work on it is finished, Open will change a ticket's status to "open", Take makes you the ticket's owner, and Extract Article is part of RT's integration with the knowledgebase RTFM (if that's installed).
In the upper right corner of the main window, new tickets will offer by default (depending on user rights) the Actions: Reply, Comment, Forward, Open It, Resolve, Reject, Delete, Take, and Extract Article. Reply and Comment will be covered shortly, in the [[ManualUsingWebInterface#Replying_and_commenting|Replying and Commenting]] section. Resolve means to close a ticket because work on it is finished, Open will change a ticket's status to "open", Take makes you the ticket's owner, and Extract Article is part of RT's integration with the knowledgebase Articles.


If anyone owns a ticket, the Take option disappears; likewise, once a ticket is resolved, the Resolve option disappears. If a resolved ticket is reopened with the Open option, Open disappears and Resolve reappears.
If anyone owns a ticket, the Take option disappears; likewise, once a ticket is resolved, the Resolve option disappears. If a resolved ticket is reopened with the Open It option, Open It disappears and Resolve reappears.


The Display page sometimes has an Attachments box (not a hyperlink), which lists ticket attachments, organized by name and then by date.
The Display page sometimes has an Attachments portlet, which lists ticket attachments, organized by name and then by date.


== History ==
== History ==


This panel on -- or separate view of -- the ticket shows everything that's ever happened to the ticket, including comments, replies, attachments and status and ownership changes. [http://requesttracker.wikia.com/index.php?title=Special:NewFiles&image=RT_3-8-8_Ticket_history-png screenshot]
This panel on -- or separate view of -- the ticket shows everything that's ever happened to the ticket, including comments, replies, attachments and status and ownership changes.


== Basics ==
== Basics ==


This is where you change the ticket's subject, status, time worked, time left, priority, final priority, and queue. A ticket's subject is what it sounds like; "time worked" and "time left" refer to the (total) number of minutes worked on this ticket only. If you're unclear on status, priority, or queue, refer to the RT Concepts section of [[ManualIntroduction]].
[[File:Ticket-Basics.png|Ticket Basics Page|thumb|500px]]


After changing information on the Basics page (or any other), don't forget to click the Save Changes button. [http://es.geocities.com/gpizarro1977/rtwiki/basics.gif screenshot]
This is where you change the ticket's subject, status, queue, owner, time estimated, time worked, time left, priority, and final priority. A ticket's subject is what it sounds like; "time estimated","time worked" and "time left" refer to the (total) number of minutes worked on this ticket only. If you're unclear on status, queue, owner, or priority, refer to [[ManualIntroduction#RT_concepts|RT Concepts]].


( == WIP == )
After changing information on the Basics page (or any other), don't forget to click the Save Changes button.


This is also the page where you can change values in a custom field. Your organization may create its own fields, and they come up on a ticket's Basics page. They work like any other field: you type things in them or select things from them. To create your own custom fields, see [[ManualAdministration]].
This is also the page where you can change values in a custom field. Your organization may create its own fields, and they come up on a ticket's Basics page. They work like any other field: you type things in them or select things from them. To create your own custom fields, see [[ManualAdministration]].
Line 148: Line 116:
== People ==
== People ==


This page deals with a ticket's owner, requestor, Cc(s), and Admin Cc(s). To review these roles, see the RT Concepts section of [[ManualIntroduction]].
To reach a ticket's People screen from within a ticket, click People on top submenu or, alternatively, click on the porlet's tab.


To reach a ticket's People screen from within a ticket, click People in the left side navigation bar:
This page deals with a ticket's owner, requestor, Cc(s), Admin Cc(s) and optionally, Custom Roles. To review these roles, see [[ManualIntroduction#RT_concepts|RT Concepts]].


There are two ways to add a watcher. If you know a potential watcher's email address, you can add one directly. Otherwise, you can search for them, then add whoever you've found.
There are two ways to add a watcher. If you know a potential watcher's email address, you can add one directly. Otherwise, you can search for them, then add whoever you've found.


To search for users before adding them as watchers:
To search for users before adding them as watchers:
<ul>
# look under "Find people whose"
# choose Username, Email, Name, or Organization from the first drop-down menu
# choose matches, doesn't match, is, or isn't from the second drop-down menu
# type your search term in the text box
# click the Go! button
</ul>


* look under Find people whose
If RT finds a user, their username will appear in the Add new watchers area below. You've now found your user, and you're ready to configure them as a watcher.
* choose User Id, Email, Name, or Organization from the first drop-down menu
* choose contains, doesn't contain, is, or isn't from the second drop-down menu
* type your search term in the text box
* click the Go! button
 
If RT finds a user, her username will appear in the Add new watchers area, the lower half of the gray box. You've now found your user, and you're ready to configure her as a watcher. '''NOTE:''' RT searching is case sensitive: Searching for "foo" will not find a person with the name "Foo"; searching for the group "support team" will not find the group named "Support Team".


To search for groups before adding them as watchers:
To search for groups before adding them as watchers:
<ul>
# look under "Find group whose"
# choose Name or Description from the first drop-down menu
# choose matches, doesn't match, is, or isn't from the second drop-down menu
# type your search term in the text box
# click the Go! button
</ul>


* look under Find group whose
If RT finds a group, the group name will appear in the Add new watchers area. You've now found your group, and you're ready to configure it as a watcher.
* choose Name or Description from the first drop-down menu
* choose contains, doesn't contain, is, or isn't from the second drop-down menu
* type your search term in the text box
* click the Go! button
 
If RT finds a group, the group name will appear in the Add new watchers area, the lower half of the gray box. You've now found your group, and you're ready to configure it as a watcher.


To add new watchers:
To add new watchers:
<ul>
# locate the Add new watchers section of the page
# for each watcher you're adding, choose Requestor, Cc, or [[AdminCC]] from the Type drop-down menu
# type the new watcher's email address in the Email text box, if it's not already filled in
# click the Save Changes button
</ul>


* locate the Add new watchers section of the page
For each email address, RT will search for an existing user to match it. If there is no match, RT will create a new unprivileged user.
* for each watcher you're adding, choose Requestor, Cc, or [[AdminCC]] from the Type drop-down menu
* type the new watcher's email address in the Email text box, if it's not already filled in
* click the Save Changes button
 
For each email address, RT will search for an existing user to match it. If there is no match, RT will create a new non-staff user. (If the user is already filled in from a search, it won't be automatically created)


To remove a watcher:
To remove a watcher:
 
<ul>
* locate the Current Watchers section of the page
# locate the Current Watchers section of the page
* check the box next to the watcher(s) to delete
# check the box next to the watcher(s) to delete
* click the Save Changes button
# click the Save Changes button
</ul>


To assign a ticket or change its owner:
To assign a ticket or change its owner:
<ul>
# change Owner drop-down menu to the person of your choice
# click the Save Changes button
</ul>


* change Owner drop-down menu to the person of your choice
To change a ticket's owner to yourself, click Take from within a ticket, this only works if the ticket was assigned to Nobody. Once a ticket is taken, the Take option disappears from the ticket's interface. If the ticket already has an owner, you can click "Steal" instead to own it. There is no intermediate "Are you sure you want to do this?" page, but if you wrongly take a ticket, you can always give it back.
* click the Save Changes button
 
To change a ticket's owner to yourself, click Take from within a ticket. Generally, you can only take a ticket that is owned by Nobody. There is no intermediate "Are you sure you want to do this?" page, but if you wrongly take a ticket, you can always give it back. Once a ticket is taken, the Take option disappears from the ticket's interface.
 


== Relationships/Links ==
==Links ==


Relationships in RT include Depends on, Depended on by, Parents, Children, Refers to, and Referred to by. If we just lost you, see the RT Concepts section of [[ManualIntroduction]]. For the sake of space, relationships are sometimes called Links in RT, such as in the left side navigation bar from within a ticket.
Links in RT include Depends on, Depended on by, Parents, Children, Refers to, and Referred to by. If we just lost you, see [[ManualIntroduction#RT_concepts|RT Concepts]].  


To reach a ticket's Relationships page:
To reach a ticket's Links page, from within a ticket, click on the Links portlet tab or Links on the ticket submenu.


* from within a ticket, click Links in the left side nav bar
You can add or delete links here, or merge duplicate tickets. In this screen shot, the links page for ticket #2, you'll see that ticket #2 is a child of parent ticket #3.


You can add or delete relationships here, or merge duplicate tickets. In this screen shot, the relationships/links page for ticket #4, you'll see that ticket #4 refers to ticket #1.
[[File:Ticket-Links.png|Ticket Links Page|thumb|500px]]


To merge two identical, duplicate tickets:
To merge two identical, duplicate tickets:
 
<ul>
* look under New Links
# look under Merge
* enter only one ticket number in the Merge Into: text box
# enter only one ticket number in the Merge Into: text box
* click the Submit button
# click the Submit button
</ul>


If someone tries to use the ticket ID of a ticket you've merged into another one, RT automatically redirects to the correct, newly-merged ticket.
If someone tries to use the ticket ID of a ticket you've merged into another one, RT automatically redirects to the correct, newly-merged ticket.


To add a relationship (Depends on, Depended on by, Parents, Children, Refers to, Referred to by):
To add a link (Depends on, Depended on by, Parents, Children, Refers to, Referred to by):
<ul>
# look under New Links
# enter ticket numbers (or other data) into the appropriate fields, separating multiple entries with spaces
# click the Submit button
</ul>


* look under New Relationships
To delete a link:
* enter ticket numbers (or other data) into the appropriate fields, separating multiple entries with spaces
<ul>
* click the Submit button
# look under Current Links
# check the box next to the link to delete
# click the Submit button
</ul>


To delete a relationship:
To add a link to an Article, see [[ManualUsingWebInterface#Replying_and_commenting|Replying and Commenting]].
 
* look under Current Relationships
* check the box next to the relationship to delete
* click the Submit button
 
To add a relationship to an RTFM article, see Replying and Commenting in this chapter.


== Jumbo ==
== Jumbo ==


This page shows editable versions of the Basics, Dates, People, and Relationships screens on one page, plus Update Ticket fields for adding comments or replies. This screen is useful if you must modify several aspects of a ticket at once. Be sure to click the Save Changes button when you're done.
This page shows editable versions of the Basics, Dates, People, and Links (and Custom Fields if added) screens on one page, plus Update Ticket fields for adding comments or replies. This screen is useful if you must modify several aspects of a ticket at once. Be sure to click the Save Changes button when you're done.
 
'''NOTE:''' For the rest of this chapter, when we say something like "from within the ticket's History page..." that means you should click History to get there, if you're not there already. If you don't see a History link to click, that likely means you're not in the ticket yet. If you're already in the History page, you don't have to click History again, of course. See the Tickets interface section earlier in this chapter if this is confusing you.


= Common tasks =
= Common tasks =
Line 246: Line 219:


To create a new ticket, start by selecting its queue:
To create a new ticket, start by selecting its queue:
 
<ul>
* from any page, select the queue of your choice from the New ticket in drop-down menu near the top of the screen
# from any page, select the queue of your choice from the "New ticket in" drop-down menu on the top right of the screen
* click the New Ticket in button
# click the New Ticket in button
</ul>
[[File:Ticket-Create.png|Ticket Create Page|thumb|500px]]


The next page will be the Create a new ticket page, defaulting to the Show basics view with the following fields:
The next page will be the Create a new ticket page, defaulting to the Show basics view with the following fields:


* Queue: this should already be filled in for you.
* Queue: this should already be filled in for you.
* Status: generally, you'll leave this at the default, new. However, you might sometimes need to create a ticket to record a past occurrence or a problem that's already being worked on, so you might choose one of the other options from the drop-down menu.
* Status: generally, you'll leave this at the default, new. However, you might sometimes need to create a ticket to record a past occurrence or a problem that's already being worked on, so you might choose one of the other statuses from the drop-down menu.
* Owner: you can give the ticket an owner or leave this blank and let someone claim it later.
* Owner: you can give the ticket an owner or leave this blank and let someone claim it later.
* You may also see some Custom Fields here if you created any and applied them to the queue
* Requestors: the default email address will be yours. Fill in any others if needed.
* Requestors: the default email address will be yours. Fill in any others if needed.
* Cc and Admin Cc: if you don't know what these are for, see the RT Concepts section in Chapter 1: Introduction.
* Cc and Admin Cc: if you don't know what these are for, see [[ManualIntroduction#RT_concepts|RT Concepts]].
* You may also see some Custom Roles here if you created any and applied them to the queue
* Subject and Attach file should look familiar to most email users and work basically the same way.
* Subject and Attach file should look familiar to most email users and work basically the same way.
* Describe the issue below means you should explain why this ticket exists.
* Describe the issue below means you should explain why this ticket exists.


If you click Show details or scroll to the bottom of the page, you'll be brought to the optional but potentially useful fields Priority, Final Priority, Time Worked, Time Left, fields for dates (Starts and Due), and fields for each relationship (Depends on, Depended on by, Parents, Children, Refers to, Referred to by). These, too, are explained in the RT Concepts section in [[ManualIntroduction]].
If you click Details from the top submenu, you'll be brought to the optional but potentially useful fields Priority, Final Priority, Time Estimated, Time Worked, Time Left, fields for dates (Starts and Due), and fields for each link (Depends on, Depended on by, Parents, Children, Refers to, Referred to by). These, too, are explained in [[ManualIntroduction#RT_concepts|RT Concepts]].


When you're done filling in fields, click the Create button to make the ticket. Clicking Show Basics brings you back to the top of the page.
When you're done filling in fields, click the Create button to make the ticket.


== Replying and commenting ==
== Replying and commenting ==
Line 268: Line 245:
There are two ways you can respond to a ticket. By default, a reply is public and a comment is hidden from the requestor. Comments and replies are listed permanently under the ticket's History.
There are two ways you can respond to a ticket. By default, a reply is public and a comment is hidden from the requestor. Comments and replies are listed permanently under the ticket's History.


To say something about a ticket, first make sure you are within one of the ticket's pages (Display, History, Basics...) then click Comment or Reply in the upper right of the page. To quote the text of an existing comment or reply, click Reply or Comment next to an existing reply or comment, from within the ticket's History, to quote the text of the existing reply or comment inline.
To say something about a ticket, first make sure you are within one of the ticket's pages (Display, History, Basics...) then click Comment or Reply in the Actions menu at the upper right of the page. To quote the text of an existing comment or reply inline, click Reply or Comment next to an existing reply/comment, from within the ticket's History (see screenshot).
 
[[File:Ticket-Txn.png|Reply, Comment or Forward in Ticket History|thumb|500px]]


You'll see drop-down menus for Status and Owner. You probably won't need to change the defaults here.
On the resulting Ticket Update page, you'll see drop-down menus for Status and Owner. You probably won't need to change the defaults here.


There will also be a text box for how many minutes the ticket has been worked on. Fill this in if you want to or if you are supposed to be logging your time.
There will also be a text box for how many minutes the ticket has been worked on. Fill this in if you want to or if you are supposed to be logging your time.


The Update Type drop-down menu will be automatically set to Comments (Not sent to requestors) or Response to requestors, depending on whether you clicked Comment or Reply as your first step. You can select the other option if you've changed your mind.
The Update Type drop-down menu will be automatically set to Comments (Not sent to requestors) or Response to requestors, depending on whether you clicked Comment or Reply as your first step. You can select the other option if you've changed your mind. As a visual aid, the message box will be yellow for comments and red for replies.


As for the other fields, we'll assume you have a working knowledge of email. RT correspondence has some fields that should be familiar to email users, such as Subject, CC, BCC, Attachments, and Message. The Subject field may be automatically filled in with the name of the ticket.
As for the other fields, we'll assume you have a working knowledge of email. RT correspondence has some fields that should be familiar to email users, such as Subject, CC, BCC, Attachments, and Message. The Subject field may be automatically filled in with the name of the ticket.
Line 280: Line 259:
'''NOTE:''' email addresses in the CC and BCC fields of replies and comments will not automatically receive future updates.
'''NOTE:''' email addresses in the CC and BCC fields of replies and comments will not automatically receive future updates.


Enter your comment or reply in the Message field, and when everything's done, click the Submit button
Enter your comment or reply in the Message field, and when everything's done, click the Submit button.


You'll be brought back to the ticket's Display page, with a status message on top that says your comment or reply has been sent/recorded, or that there is a problem and it hasn't.
You'll be brought back to the ticket's Display page, with a status message on top that says your comment or reply has been sent/recorded, or that there is a problem and it hasn't.


To add a signature that will appear by default at the bottom of all your comments and replies:
To add a signature that will appear by default at the bottom of all your comments and replies:
<ul>
# click Logged in as -> Settings -> About Me from the top navigation bar
# type your (preferably short) signature in the Signature field
# click the Save Preference
</ul>


* click Preferences in the upper right, or in the left side navigation bar
=== Reply and comment with Articles ===
* type your (preferably short) signature in the Signature field
* click the Submit button
 
=== Reply and comment integration with RTFM ===


RTFM is RT's integrated knowledgebase system. If you are using RTFM, you should know that when you reply to or comment on tickets in RT, you can search for and include (editable) RTFM articles in the reply or comment. The ticket will now have a new relationship: Refers To (article of your choice). This screen shot shows the relevant part of the Reply or Comment screen, located under Attach in the Message portion of the page:
[[File:Ticket-Update-Articles.png|Add Articles to Reply/Comment|thumb|500px]]


[screenshot]
Articles is RT's knowledgebase system. If you are using Articles, you should know that when you reply to or comment on tickets in RT, you can search for and include (editable) Articles in the reply or comment. The ticket will now have a new link: Refers To (article of your choice). This screen shot shows the relevant part of the Reply or Comment screen, located above the Message box of the page:


If you know the name or number of the article you'd like to include, enter it in the Include RTFM article text box and click the Go button.
To find an Article to include in the reply or comment, enter a search term in the "Search for Articles matching" text box and click the Go button. Assuming there are search results, click the Go button next to the article you'd like to include.


To find an RTFM article to include in the reply or comment, enter a search term in the Search for RTFM articles matching text box and click the Go button. Assuming there are search results, click the Go button next to the article you'd like to include.
If you know the name or id of the article you'd like to include, enter it in the Include Article text box and click the Go button.


== Modifying a ticket ==
== Modifying a ticket ==
Line 304: Line 284:
Listed alphabetically by item that could be changed:
Listed alphabetically by item that could be changed:


* due date (or any other date):
* dates:
** from with a ticket's Dates page, type the new date in the <code>Due:</code> text box
:# click on the Dates portlet or menu item on ticket display
** click the Submit button
:# type the new date in the <code>Starts</code> or <code>Due</code> text box, <code>Started</code> and <code>Last Contact</code> can also be manually updated
* final priority:
:# click the Save Changes button
** from within a ticket's Basics page, type a new number in the Final Priority field
* history: a ticket's history cannot be changed.
** click the Save Changes button
* history: we're sorry, a ticket's history cannot be changed.
* owner:
* owner:
** from within a ticket's People page, change Owner in drop-down menu to the person of your choice
:# from within a ticket's People page, change <code>Owner</code> in drop-down menu to the person of your choice
** click the Save Changes button
:# click the Save Changes button
* priority:
* priorities:
** from within a ticket's Basics page, type a new number in the Priority field
:# from within a ticket's Basics page, type a new number in the <code>Priority</code>/<code>Final Priority</code> fields
** click the Save Changes button
:# click the Save Changes button
* queue:
* queue:
** from within a ticket's Basics page, select a new item from the Queue drop-down menu
:# from within a ticket's Basics page, select a new item from the <code>Queue</code> drop-down menu
** click the Save Changes button
:# click the Save Changes button
** '''NOTE:''' that when you change a ticket's queue, queue-specific values such as custom fields will disappear. They will not be deleted, but they will be hidden.
:# '''NOTE:''' that when you change a ticket's queue, queue-specific values such as custom fields will disappear. They will not be deleted, but they will be hidden.
* status:
* status:
** from within a ticket's Basics page, select a value from the Status drop-down menu
:# from within a ticket's Basics page, select a value from the <code>Status</code> drop-down menu
** click the Save Changes button
:# click the Save Changes button
* subject:
* subject:
** from within a ticket's Basics page, type new data in the Subject field
:# from within a ticket's Basics page, type new data in the <code>Subject</code> field
** click the Save Changes button
:# click the Save Changes button
* time left:
* time fields:
** from within a ticket's Basics page, type a new number in the Time Left field
:# from within a ticket's Basics page, type a new number in the <code>Time Estimated</code>/<code>Time Worked</code>/<code>Time Left</code> fields
** click the Save Changes button
:# click the Save Changes button
* time worked:
** from within a ticket's Basics page, type a new number in the Time Worked field
** click the Save Changes button


== Modifying people ==
== Modifying people ==
Line 338: Line 313:
To assign a ticket or change its owner:
To assign a ticket or change its owner:


* from a ticket's People page, change Owner in drop-down menu to the person of your choice
:# from a ticket's People page, change Owner in drop-down menu to the person of your choice
* click the Save Changes button
:# click the Save Changes button


To add new watchers:
To add new watchers:


* from a ticket's People page, locate the Add New Watchers section of the page
:# from a ticket's People page, locate the "Add New Watchers" section of the page
* choose Requestor, Cc, or [[AdminCc]] from the Type drop-down menu
:# choose Requestor, Cc, AdminCc or any Custom Role from the Type drop-down menu
* type the new watcher's email address in the Email text box
:# type the new watcher's email address in the Email text box
* add up to two more watchers, for a total of up to three
:# add up to two more watchers, for a total of up to three
* click the Save Changes button
:# click the Save Changes button


To remove a watcher:
To remove a watcher:


* from a ticket's People page, locate the Current Watchers section of the page
:# from a ticket's People page, locate the Current Watchers section of the page
* check the box next to the watcher(s) to delete
:# check the box next to the watcher(s) to delete
* click the Save Changes button
:# click the Save Changes button


== Modifying relationships ==
== Modifying Links ==


To add a relationship (Depends on, Depended on by, Parents, Children, Refers to, Referred to by):
To add a link (Depends on, Depended on by, Parents, Children, Refers to, Referred to by):


* from within a ticket's Relationships (or Links) page, look under New Relationships
:# from within a ticket's Links page, look under New Links
* enter ticket numbers (or other data) into the appropriate fields, separating multiple entries with spaces
:# enter ticket ids (or other data) into the appropriate fields, separating multiple entries with spaces
* click the Submit button
:# click the Save Changes button


To delete a relationship:
To delete a link:


* from within a ticket's Relationships (or Links) page, look under Current Relationships
:# from within a ticket's Links page, look under Current Links
* check the box next to the relationship to delete
:# check the box next to the link to delete
* click the Submit button
:# click the Save Changes button


To merge a duplicate ticket into an identical ticket:
To merge a duplicate ticket into an identical ticket:


* from within a ticket's Relationships (or Links) page, look under New Relationships
:# from within a ticket's Links page, look under Merge
* enter only one ticket number in the Merge Into: text box
:# enter only one ticket id in the Merge Into: text box
* click the Submit button
:# click the Save Changes button


If someone tries to use the ticket ID of a ticket you've merged into another one, RT automatically redirects to the correct, newly-merged ticket. Merging tickets also merges all ticket data such as watchers, relationships, and history.
If someone tries to use the ticket ID of a ticket you've merged into another one, RT automatically redirects to the correct, newly-merged ticket. Merging tickets also merges all ticket data such as watchers, links, and history.


== Updating many tickets at once ==
== Updating many tickets at once ==


Sometimes, you may need to make a change to several tickets at once. There's an easy way to do this: locate the tickets you want (see the Searching section of this chapter for help) -&gt; click Update all these tickets at once
Sometimes, you may need to make a change to several tickets at once. There's an easy way to do this:
 
:# locate the tickets you want (see [[ManualUsingWebInterface#Searching_for_tickets|Searching for tickets]])
You'll be sent to a Bulk ticket update page where you can add a comment or reply to all the tickets, or change the tickets' owner, requestors, Cc, Admin Cc, subject, priority, queue, status, start date, due date, and resolved date. The power!
:# from the results page, click "Bulk Update" from the top submenu
 
:# you'll be sent to a Bulk ticket update page where you can add a comment or reply to all the tickets, or change the tickets' owner, requestors, Cc, Admin Cc, subject, priority, queue, status, and various date fields. The power!
Click the Submit button when you're done.
:# click the Update button


== Resolving a ticket ==
== Resolving a ticket ==


If a ticket has been completed and doesn't need any more work, you can resolve it by clicking Resolve in the upper right of one of the ticket's pages (Display, History, Basics...).
If a ticket has been completed and doesn't need any more work, you can resolve it by clicking Resolve in Actions menu of ticket's pages (Display, History, Basics...).


This takes you to a comment form (see above Replying and Commenting section) but sets the Status drop-down menu to Resolved.
This takes you to a comment form (see [[ManualUsingWebInterface#Replying_and_commenting|Replying and Commenting]]) but sets the Status drop-down menu to Resolved.


You're encouraged to use the Message text box to explain why you're resolving the ticket.
You're encouraged to use the Message text box to explain why you're resolving the ticket.


When you're done, click the Submit button.
When you're done, click the Update Ticket button.


You'll be brought to the ticket's Display page and told the comment has been recorded and ticket has been resolved (or not, if there is a problem).
You'll be brought to the ticket's Display page and told the comment has been recorded and ticket has been resolved (or not, if there is a problem).
Line 399: Line 374:
== Changing your own user information ==
== Changing your own user information ==


To change your own name, email address, phone numbers, location, or signature:
[[File:About-Me.png|About Me Page|thumb|500px]]


* click Preferences in the upper right of the screen or in the left side navigation bar
To change your own name, email address, phone numbers, location, signature or password:
* type new information in the desired fields
* click the Submit button


To change your own password:
:# in the upper right of the screen, click Logged in as -> Settings -> About Me
:# type new information in the desired fields
:# click the Save Preferences button


* click Preferences in the upper right of the screen or in the left side navigation bar
'''NOTE:''' You'll need the right "ModifySelf" to view this page and make changes.
* type the new password in the New Password text box
* type it again in the Retype Password text box
* click the Submit button


== Personal groups ==
== Groups ==


Users can grant their rights to others by creating a personal group and delegating the rights to the members of that group. This is convenient if you're going on vacation or need to pass the buck for any reason.
Users can grant their rights to others by creating a group and delegating the rights to the members of that group. This is convenient if you're going on vacation or need to pass the buck for any reason.


First of all go to:
To view existing groups, go to Admin -> Groups -> Select -> [select group name]


* click Preferences
To make a new group:
* click Personal Groups


To make a new personal group:
:# go to Admin -> Groups -> Create
:# type your group's name and description in the <code>Name:</code> and <code>Description:</code> text boxes
:# click the Create button


* click New group in the left side navigation bar
To add members to a group:
* type your group's name and description in the <code>Name:</code> and <code>Description:</code> text boxes
* click the Submit button


To add members to a personal group:
:# click the name of a group
:# click Members from the top submenu
:# select user(s) or group(s) from the Add members are
:# click the Modify Members button


* click the name of a personal group
To delete members from a group:
* click Members in the left side navigation bar
* select user(s) or group(s) from the Add members box
* click the Submit button


To delete members from a personal group:
:# click the name of a group
:# click Members from the top submenu
:# check the box next to the user(s) or group(s) to delete
:# click the Modify Members button


* click the name of a personal group
To change a group's name or description:
* click Members in the left side navigation bar
* check the box next to the user(s) or group(s) to delete
* click the Submit button


To change a personal group's name or description:
:# click the name of a group
 
:# make changes
* click the name of a personal group
:# click the Save Changes button
* make changes
* click the Submit button


To disable a personal group:
To disable a personal group:


* click the name of a personal group
:# click the name of a group
* clear the Enabled checkbox
:# clear the Enabled checkbox
* click the Submit button
:# click the Save Changes button


Unlike disabled users and queues, disabled personal groups will still be visible in listings. That removes a step from the process of re-enabling them when necessary.
Unlike disabled users and queues, disabled groups will still be visible in listings. That removes a step from the process of re-enabling them when necessary.


To re-enable a personal group:
To re-enable a group:


* click the name of a personal group
:# click the name of a group
* check the Enabled checkbox
:# check the Enabled checkbox
* click the Submit button
:# click the Save Changes button


== Delegating ==
== Rights ==
[[File:Group-Rights.png|Group Rights Page|thumb|500px]]


Once you have a personal group, you can delegate rights.
Once you have a group, you can grant rights.


* In order to delegate rights, you'll need to have the right "Delegate Rights."
* In order to delegate rights, you'll need to have the right "ShowConfigTab", which allows you to view the Admin menu in the top navigation bar
* If you've been granted a right and you delegate it to someone, then someone revokes your right, that also revokes your delegate's right.
* If you've been granted a right globally, you can't delegate it for just one queue and vice versa.
* If you've been granted a right globally, you can't delegate it for just one queue and vice versa.


[screenshot]
To grant rights to a group:
 
To delegate rights to a personal group:


* click Preferences
:# go to Admin -> Global -> Group Rights
* click Delegation
:# on the left side of the page, select a system group, role, or user group listed, or search for a group under "Add Group"
* locate the right(s) you'd like to delegate
:# rights are grouped by "General Rights", "Rights for Staff" and "Rights for Administrators", these are suggested rights, but you may grant whichever from any of the tabs
* check the box next to the right(s) and under the correct personal group(s)
:# check the box(es) next to the right(s) you'd like to grant
* click the Submit button
:# click the Save Changes button


To stop delegating rights to a personal group:
To revoke rights on a group:


* click Preferences
:# go to Admin -> Global -> Group Rights
* click Delegation
:# on the left side of the page, select a system group, role, or user group listed, or search for a group under "Add Group"
* locate the correct right(s)
:# uncheck the box(es) next to the right(s) you'd like to revoke
* clear the checkbox next to the right(s) and under the correct personal group(s)
:# click the Save Changes button
* click the Submit button


== Logging out ==
== Logging out ==
Line 491: Line 457:
You can leave yourself logged into RT without breaking anything, but logging out is a good habit to get into for security purposes. Logging out is standard:
You can leave yourself logged into RT without breaking anything, but logging out is a good habit to get into for security purposes. Logging out is standard:


* click Logout in the upper right hand corner of the page.
* click Logged in as -> Logout in the top navigation bar


Some RT configurations don't have a Logout button, so don't panic if you don't see one.
Some RT configurations don't have a Logout button, so don't panic if you don't see one.
Line 499: Line 465:
Prev: [[ManualBasicAdministration]] --- Up: [[UserManual]] --- Next: [[ManualAdministration]]
Prev: [[ManualBasicAdministration]] --- Up: [[UserManual]] --- Next: [[ManualAdministration]]
[[Category:RT User Manual]]
[[Category:RT User Manual]]
[[Category:RT44]]

Latest revision as of 15:50, 28 March 2019

Prev: ManualBasicAdministration --- Up: UserManual --- Next: ManualAdministration


RT has a web interface that works in just about every web browser - including screen readers for the blind - and is easy to use. How easy? You're about to find out. Remember, though, that RT is very configurable; if you're reading this to learn how to use a local installation at your site, remember that your administrator could have made changes that will make things look differently than they do here; don't let it throw you.

RT has a powerful interface to create queries using TicketSQL, a SQL-like syntax for searching tickets. The output format can also be configured. i.e. which columns to show. This can be configured using the query builder or a plain text input in advanced mode.

If you see any unfamiliar terms in this chapter, look for them in the RT Concepts section of ManualIntroduction, or in RTGlossary.

This manual is being updated to 4.4; we're going to snip out references to things that were markedly different in older -- particularly pre-4.x -- releases. If you have one of those... you really need to think about upgrading.

Logging In

Your administrator will tell you where your login page is, and what username and (usually) temporary password to use. The login screen looks like this:

RT Login Page

Type your username in the Username text box, type your password in the Password text box, and then click the Login button, or hit ENTER.

RT at a Glance (Home Page)

Immediately after logging in, you'll be looking at the home page, RT at a Glance.

RT at a Glance

NOTE: You'll find that many items are clickable hotlinks in the RT interface, such as ticket ids and queues, but the default interface configuration does not highlight these using the usual blue color or underline. Move your mouse around; things which are links will get an underline when you hover the mouse over them. Clicking on these items takes you pretty much where you might expect it would.

Also, note that your installation may have been customized by the administrator, and because of that, things may be in different places than we describe here.

The main part of the page, called "RT at a Glance", will contain a collection of panels, each of which can be minimized, and some of which can also be edited.

By default, these are:

In the left column

  • 10 highest priority tickets I own: This section displays what you need to do. Each ticket will display its id, subject, queue, and status from this page. Click any ticket's id or description to display its basic information page (see also the Tickets interface section of this chapter).
  • 10 newest unowned tickets: Here you'll see the list of tickets which have been created, but not yet assigned to anyone, sorted with the newest ones at the top. Each ticket has an associated Take link which you can use to assign the ownership of the ticket to yourself, and start working on it.
  • Bookmarked tickets: Here is a facility where you can bookmark any ticket while you're looking at it, no matter its queue or owner, by clicking on an empty star in the top right corner of the page. Tickets you've bookmarked in this way will be displayed in this panel.
  • Quick Ticket Creation: This panel lets you enter the bare minimum of information about a new ticket, to create one quickly when necessary. If you need to enter more information about a new ticket, including things like CCs, select a queue from the top submenu of the page, and click the "New Ticket In" button; this will give you the complete New Ticket screen.

In the right column

  • My Reminders - If you have set a reminder for yourself in a ticket, you will see the title of the reminder and which ticket it belongs to. Click on the title of the reminder to follow it.
  • Queue List - This panel contains a list of all the queues you're permitted to access, logged in with the current user account. They're in alphabetical order, and show tickets in each status based on the queue lifecycle.
  • Dashboards: The Dashboards panel (see ManualDashboards) will contain a list of any Dashboards which have been created for the entire RT installation, your user group, or your personally created dashboards.
  • Refresh: This pulldown menu, on the lower right side of the screen, lets you select whether the homepage is automatically refreshed or not. The default is no. Other options are refreshing the page every 2, 5, 10, 20, 60, and 120 minutes. Click the Go! button to select the displayed auto-refresh delay.

Top navigation bar

This is the RT main menu. The options will expand into a menu tree as you select various tasks. Your current location in this tree will always be boldfaced. Some of these options may not be displayed if you do not have the appropriate rights.

  • Home: the home page: where you are now. You can always get back to the home page by clicking Home in the upper left of the screen. You can even click this if you're on the home page, as an easy Refresh link.
  • Search: clicking this brings you to the ticket search query builder page (see also Searching for tickets).
  • Reports: This allows you to quickly create reports on tickets Resolved by owner, Resolved in date range or Created in a date range.
  • Articles: clicking this takes you to Articles, RT's integrated knowledgebase.
  • Assets: Assets allow you to keep an inventory of items that can then be linked to tickets as needed
  • Tools: The options here allow you to view your daily progress, check your reminder and view any approvals you may need
  • Admin: This link takes administrators to the section of RT where they can configure users, queues and scrips, and make global setup changes to the installation.
  • Logged in as: This menu lets you configure RT for your personal tastes. You can also log out of RT here.

Top submenu

  • New ticket in: Use this to quickly start creating a ticket (for more detail, see Creating a new ticket). Choose a queue from the drop-down menu and click the "New ticket in:" button to begin.
  • Search: Type a search term in the text box and click the Search button to find tickets. This box can do some magic, for example you can type in a ticket id, and jump directly to that ticket. Check out ManualSimpleSearch for more on the magic and ManualSearchTickets for more ways to search tickets.

Tickets interface

The fundamental object in RT is the ticket; a ticket groups all of the information about, and transactions related to, an issue you're using RT to track.

First, you should know some of the various ways to navigate to an existing ticket:

  • from the Home page, click a ticket subject under 10 highest priority tickets I own or 10 newest unowned tickets. Or, you can Take an unowned ticket, which has the extra side effect of assigning ownership to you.
  • search for a ticket, from the search box on the Home page or by clicking Search in the top navigation bar, then click on the ticket.
  • click a queue name on the Queue List panel and then click a ticket.
  • clicking a ticket's URL from within an email message.

Display

Any way you navigate to a ticket, you'll arrive at that ticket's Display page first.

The Display view, the first of many possible views of the ticket, (see screenshot) provides an overview of the ticket.

Ticket Display Page

Two panes come up on the Display view: Ticket Metadata on top, and History below.

As you can see, it includes information like Basics, People, Reminders, Dates, and Links, each in it's own portlet.

The id and subject of the ticket is above the top command bar.

In the upper right corner of the main window, new tickets will offer by default (depending on user rights) the Actions: Reply, Comment, Forward, Open It, Resolve, Reject, Delete, Take, and Extract Article. Reply and Comment will be covered shortly, in the Replying and Commenting section. Resolve means to close a ticket because work on it is finished, Open will change a ticket's status to "open", Take makes you the ticket's owner, and Extract Article is part of RT's integration with the knowledgebase Articles.

If anyone owns a ticket, the Take option disappears; likewise, once a ticket is resolved, the Resolve option disappears. If a resolved ticket is reopened with the Open It option, Open It disappears and Resolve reappears.

The Display page sometimes has an Attachments portlet, which lists ticket attachments, organized by name and then by date.

History

This panel on -- or separate view of -- the ticket shows everything that's ever happened to the ticket, including comments, replies, attachments and status and ownership changes.

Basics

Ticket Basics Page

This is where you change the ticket's subject, status, queue, owner, time estimated, time worked, time left, priority, and final priority. A ticket's subject is what it sounds like; "time estimated","time worked" and "time left" refer to the (total) number of minutes worked on this ticket only. If you're unclear on status, queue, owner, or priority, refer to RT Concepts.

After changing information on the Basics page (or any other), don't forget to click the Save Changes button.

This is also the page where you can change values in a custom field. Your organization may create its own fields, and they come up on a ticket's Basics page. They work like any other field: you type things in them or select things from them. To create your own custom fields, see ManualAdministration.

Dates

ManualTicketDates

People

To reach a ticket's People screen from within a ticket, click People on top submenu or, alternatively, click on the porlet's tab.

This page deals with a ticket's owner, requestor, Cc(s), Admin Cc(s) and optionally, Custom Roles. To review these roles, see RT Concepts.

There are two ways to add a watcher. If you know a potential watcher's email address, you can add one directly. Otherwise, you can search for them, then add whoever you've found.

To search for users before adding them as watchers:

    1. look under "Find people whose"
    2. choose Username, Email, Name, or Organization from the first drop-down menu
    3. choose matches, doesn't match, is, or isn't from the second drop-down menu
    4. type your search term in the text box
    5. click the Go! button

If RT finds a user, their username will appear in the Add new watchers area below. You've now found your user, and you're ready to configure them as a watcher.

To search for groups before adding them as watchers:

    1. look under "Find group whose"
    2. choose Name or Description from the first drop-down menu
    3. choose matches, doesn't match, is, or isn't from the second drop-down menu
    4. type your search term in the text box
    5. click the Go! button

If RT finds a group, the group name will appear in the Add new watchers area. You've now found your group, and you're ready to configure it as a watcher.

To add new watchers:

    1. locate the Add new watchers section of the page
    2. for each watcher you're adding, choose Requestor, Cc, or AdminCC from the Type drop-down menu
    3. type the new watcher's email address in the Email text box, if it's not already filled in
    4. click the Save Changes button

For each email address, RT will search for an existing user to match it. If there is no match, RT will create a new unprivileged user.

To remove a watcher:

    1. locate the Current Watchers section of the page
    2. check the box next to the watcher(s) to delete
    3. click the Save Changes button

To assign a ticket or change its owner:

    1. change Owner drop-down menu to the person of your choice
    2. click the Save Changes button

To change a ticket's owner to yourself, click Take from within a ticket, this only works if the ticket was assigned to Nobody. Once a ticket is taken, the Take option disappears from the ticket's interface. If the ticket already has an owner, you can click "Steal" instead to own it. There is no intermediate "Are you sure you want to do this?" page, but if you wrongly take a ticket, you can always give it back.

Links

Links in RT include Depends on, Depended on by, Parents, Children, Refers to, and Referred to by. If we just lost you, see RT Concepts.

To reach a ticket's Links page, from within a ticket, click on the Links portlet tab or Links on the ticket submenu.

You can add or delete links here, or merge duplicate tickets. In this screen shot, the links page for ticket #2, you'll see that ticket #2 is a child of parent ticket #3.

Ticket Links Page

To merge two identical, duplicate tickets:

    1. look under Merge
    2. enter only one ticket number in the Merge Into: text box
    3. click the Submit button

If someone tries to use the ticket ID of a ticket you've merged into another one, RT automatically redirects to the correct, newly-merged ticket.

To add a link (Depends on, Depended on by, Parents, Children, Refers to, Referred to by):

    1. look under New Links
    2. enter ticket numbers (or other data) into the appropriate fields, separating multiple entries with spaces
    3. click the Submit button

To delete a link:

    1. look under Current Links
    2. check the box next to the link to delete
    3. click the Submit button

To add a link to an Article, see Replying and Commenting.

Jumbo

This page shows editable versions of the Basics, Dates, People, and Links (and Custom Fields if added) screens on one page, plus Update Ticket fields for adding comments or replies. This screen is useful if you must modify several aspects of a ticket at once. Be sure to click the Save Changes button when you're done.

Common tasks

Now that you know your way around RT's web interface, there are probably many tasks you can figure out on your own. However, we wanted to make sure you had a step-by-step guide to the most important and common tasks such as using RT's search functionality and working with tickets.

Searching for tickets

ManualSearchTickets

Creating a new ticket

To create a new ticket, start by selecting its queue:

    1. from any page, select the queue of your choice from the "New ticket in" drop-down menu on the top right of the screen
    2. click the New Ticket in button
Ticket Create Page

The next page will be the Create a new ticket page, defaulting to the Show basics view with the following fields:

  • Queue: this should already be filled in for you.
  • Status: generally, you'll leave this at the default, new. However, you might sometimes need to create a ticket to record a past occurrence or a problem that's already being worked on, so you might choose one of the other statuses from the drop-down menu.
  • Owner: you can give the ticket an owner or leave this blank and let someone claim it later.
  • You may also see some Custom Fields here if you created any and applied them to the queue
  • Requestors: the default email address will be yours. Fill in any others if needed.
  • Cc and Admin Cc: if you don't know what these are for, see RT Concepts.
  • You may also see some Custom Roles here if you created any and applied them to the queue
  • Subject and Attach file should look familiar to most email users and work basically the same way.
  • Describe the issue below means you should explain why this ticket exists.

If you click Details from the top submenu, you'll be brought to the optional but potentially useful fields Priority, Final Priority, Time Estimated, Time Worked, Time Left, fields for dates (Starts and Due), and fields for each link (Depends on, Depended on by, Parents, Children, Refers to, Referred to by). These, too, are explained in RT Concepts.

When you're done filling in fields, click the Create button to make the ticket.

Replying and commenting

There are two ways you can respond to a ticket. By default, a reply is public and a comment is hidden from the requestor. Comments and replies are listed permanently under the ticket's History.

To say something about a ticket, first make sure you are within one of the ticket's pages (Display, History, Basics...) then click Comment or Reply in the Actions menu at the upper right of the page. To quote the text of an existing comment or reply inline, click Reply or Comment next to an existing reply/comment, from within the ticket's History (see screenshot).

Reply, Comment or Forward in Ticket History

On the resulting Ticket Update page, you'll see drop-down menus for Status and Owner. You probably won't need to change the defaults here.

There will also be a text box for how many minutes the ticket has been worked on. Fill this in if you want to or if you are supposed to be logging your time.

The Update Type drop-down menu will be automatically set to Comments (Not sent to requestors) or Response to requestors, depending on whether you clicked Comment or Reply as your first step. You can select the other option if you've changed your mind. As a visual aid, the message box will be yellow for comments and red for replies.

As for the other fields, we'll assume you have a working knowledge of email. RT correspondence has some fields that should be familiar to email users, such as Subject, CC, BCC, Attachments, and Message. The Subject field may be automatically filled in with the name of the ticket.

NOTE: email addresses in the CC and BCC fields of replies and comments will not automatically receive future updates.

Enter your comment or reply in the Message field, and when everything's done, click the Submit button.

You'll be brought back to the ticket's Display page, with a status message on top that says your comment or reply has been sent/recorded, or that there is a problem and it hasn't.

To add a signature that will appear by default at the bottom of all your comments and replies:

    1. click Logged in as -> Settings -> About Me from the top navigation bar
    2. type your (preferably short) signature in the Signature field
    3. click the Save Preference

Reply and comment with Articles

Add Articles to Reply/Comment

Articles is RT's knowledgebase system. If you are using Articles, you should know that when you reply to or comment on tickets in RT, you can search for and include (editable) Articles in the reply or comment. The ticket will now have a new link: Refers To (article of your choice). This screen shot shows the relevant part of the Reply or Comment screen, located above the Message box of the page:

To find an Article to include in the reply or comment, enter a search term in the "Search for Articles matching" text box and click the Go button. Assuming there are search results, click the Go button next to the article you'd like to include.

If you know the name or id of the article you'd like to include, enter it in the Include Article text box and click the Go button.

Modifying a ticket

Listed alphabetically by item that could be changed:

  • dates:
  1. click on the Dates portlet or menu item on ticket display
  2. type the new date in the Starts or Due text box, Started and Last Contact can also be manually updated
  3. click the Save Changes button
  • history: a ticket's history cannot be changed.
  • owner:
  1. from within a ticket's People page, change Owner in drop-down menu to the person of your choice
  2. click the Save Changes button
  • priorities:
  1. from within a ticket's Basics page, type a new number in the Priority/Final Priority fields
  2. click the Save Changes button
  • queue:
  1. from within a ticket's Basics page, select a new item from the Queue drop-down menu
  2. click the Save Changes button
  3. NOTE: that when you change a ticket's queue, queue-specific values such as custom fields will disappear. They will not be deleted, but they will be hidden.
  • status:
  1. from within a ticket's Basics page, select a value from the Status drop-down menu
  2. click the Save Changes button
  • subject:
  1. from within a ticket's Basics page, type new data in the Subject field
  2. click the Save Changes button
  • time fields:
  1. from within a ticket's Basics page, type a new number in the Time Estimated/Time Worked/Time Left fields
  2. click the Save Changes button

Modifying people

To assign a ticket or change its owner:

  1. from a ticket's People page, change Owner in drop-down menu to the person of your choice
  2. click the Save Changes button

To add new watchers:

  1. from a ticket's People page, locate the "Add New Watchers" section of the page
  2. choose Requestor, Cc, AdminCc or any Custom Role from the Type drop-down menu
  3. type the new watcher's email address in the Email text box
  4. add up to two more watchers, for a total of up to three
  5. click the Save Changes button

To remove a watcher:

  1. from a ticket's People page, locate the Current Watchers section of the page
  2. check the box next to the watcher(s) to delete
  3. click the Save Changes button

Modifying Links

To add a link (Depends on, Depended on by, Parents, Children, Refers to, Referred to by):

  1. from within a ticket's Links page, look under New Links
  2. enter ticket ids (or other data) into the appropriate fields, separating multiple entries with spaces
  3. click the Save Changes button

To delete a link:

  1. from within a ticket's Links page, look under Current Links
  2. check the box next to the link to delete
  3. click the Save Changes button

To merge a duplicate ticket into an identical ticket:

  1. from within a ticket's Links page, look under Merge
  2. enter only one ticket id in the Merge Into: text box
  3. click the Save Changes button

If someone tries to use the ticket ID of a ticket you've merged into another one, RT automatically redirects to the correct, newly-merged ticket. Merging tickets also merges all ticket data such as watchers, links, and history.

Updating many tickets at once

Sometimes, you may need to make a change to several tickets at once. There's an easy way to do this:

  1. locate the tickets you want (see Searching for tickets)
  2. from the results page, click "Bulk Update" from the top submenu
  3. you'll be sent to a Bulk ticket update page where you can add a comment or reply to all the tickets, or change the tickets' owner, requestors, Cc, Admin Cc, subject, priority, queue, status, and various date fields. The power!
  4. click the Update button

Resolving a ticket

If a ticket has been completed and doesn't need any more work, you can resolve it by clicking Resolve in Actions menu of ticket's pages (Display, History, Basics...).

This takes you to a comment form (see Replying and Commenting) but sets the Status drop-down menu to Resolved.

You're encouraged to use the Message text box to explain why you're resolving the ticket.

When you're done, click the Update Ticket button.

You'll be brought to the ticket's Display page and told the comment has been recorded and ticket has been resolved (or not, if there is a problem).

Changing your own user information

About Me Page

To change your own name, email address, phone numbers, location, signature or password:

  1. in the upper right of the screen, click Logged in as -> Settings -> About Me
  2. type new information in the desired fields
  3. click the Save Preferences button

NOTE: You'll need the right "ModifySelf" to view this page and make changes.

Groups

Users can grant their rights to others by creating a group and delegating the rights to the members of that group. This is convenient if you're going on vacation or need to pass the buck for any reason.

To view existing groups, go to Admin -> Groups -> Select -> [select group name]

To make a new group:

  1. go to Admin -> Groups -> Create
  2. type your group's name and description in the Name: and Description: text boxes
  3. click the Create button

To add members to a group:

  1. click the name of a group
  2. click Members from the top submenu
  3. select user(s) or group(s) from the Add members are
  4. click the Modify Members button

To delete members from a group:

  1. click the name of a group
  2. click Members from the top submenu
  3. check the box next to the user(s) or group(s) to delete
  4. click the Modify Members button

To change a group's name or description:

  1. click the name of a group
  2. make changes
  3. click the Save Changes button

To disable a personal group:

  1. click the name of a group
  2. clear the Enabled checkbox
  3. click the Save Changes button

Unlike disabled users and queues, disabled groups will still be visible in listings. That removes a step from the process of re-enabling them when necessary.

To re-enable a group:

  1. click the name of a group
  2. check the Enabled checkbox
  3. click the Save Changes button

Rights

Group Rights Page

Once you have a group, you can grant rights.

  • In order to delegate rights, you'll need to have the right "ShowConfigTab", which allows you to view the Admin menu in the top navigation bar
  • If you've been granted a right globally, you can't delegate it for just one queue and vice versa.

To grant rights to a group:

  1. go to Admin -> Global -> Group Rights
  2. on the left side of the page, select a system group, role, or user group listed, or search for a group under "Add Group"
  3. rights are grouped by "General Rights", "Rights for Staff" and "Rights for Administrators", these are suggested rights, but you may grant whichever from any of the tabs
  4. check the box(es) next to the right(s) you'd like to grant
  5. click the Save Changes button

To revoke rights on a group:

  1. go to Admin -> Global -> Group Rights
  2. on the left side of the page, select a system group, role, or user group listed, or search for a group under "Add Group"
  3. uncheck the box(es) next to the right(s) you'd like to revoke
  4. click the Save Changes button

Logging out

You can leave yourself logged into RT without breaking anything, but logging out is a good habit to get into for security purposes. Logging out is standard:

  • click Logged in as -> Logout in the top navigation bar

Some RT configurations don't have a Logout button, so don't panic if you don't see one.


Prev: ManualBasicAdministration --- Up: UserManual --- Next: ManualAdministration