RequestTracker
Access tickets from RequestTracker
Availability depends on your school's enabled tools, provider setup, and account permissions. These settings are managed in the web workspace. A class policy may restrict a feature described here.
How it works#
The Request Tracker connector will pull in all tickets updated within the last 10 minutes into the dataset.
Tickets are updated every 10 minutes.
Only Request Tracker REST API 1.0 is supported at this time. REST API 1.0 is implemented in Request Tracker 4.x, Request Tracker 5.x is not supported currently.
Setting up#
Create or use a Request Tracker user who has the appropriate permissions#
Create a Request Tracker user that has read access to all queues Nexus should read.
Configure Request Tracker connector and begin indexing#
Open Request Tracker connector#
Navigate to the Admin Panel and select the Request Tracker Connector
Enter credentials#
In Step 1, provide your Request Tracker username, password, and RT installation base url.
Start indexing#
In Step 2, click Connect to begin indexing
Before using this source with students#
Start with approved course material. Check which documents the connector can retrieve and how it maps source permissions. Test with a student account and a teacher account before widening access. A successful sync does not prove that the intended class boundary is correct.
Use source troubleshooting when a document is missing or visible to the wrong audience.