We still need to figure out how to utilize the capabilities of RT to manage our ticket requests. (Should it interact with bugzilla, with github issues?, ) Previously it managed setting up new courses on MAA servers, managed the database for the WeBWorK sites map and fielded alerts about the status of the MAA servers, request for lost passwords, (complaints about bugs in PG problems- these were supposed to be routed to the forums) and so forth. Now is a good time to make a plan for managing The WeBWorK Project and then figure out what role RT will play and learn how to configure it to satisfy our needs.
We still need to figure out how to utilize the capabilities of RT to manage our ticket requests. (Should it interact with bugzilla, with github issues?, ) Previously it managed setting up new courses on MAA servers, managed the database for the WeBWorK sites map and fielded alerts about the status of the MAA servers, request for lost passwords, (complaints about bugs in PG problems- these were supposed to be routed to the forums) and so forth. Now is a good time to make a plan for managing The WeBWorK Project and then figure out what role RT will play and learn how to configure it to satisfy our needs.