
We have the ability to update the frequency of how often tickets come in.
After replying to an email we can resolve it, and if there is a reply the ticket will opens up again. Review collected by and hosted on G2.com.
Search takes too long to perform, especially if we search by date. Review collected by and hosted on G2.com.
One of the features that I like about Request tracker is how it enables creation of Custom Dashboards for different processes and how we can share the same with a group of people in the company who might need to see the number of tickets and the details of the tickets right in the software itself. And then comes its seamless Email integration with the Active Directory of our organization. Review collected by and hosted on G2.com.
The way how the UI looks for this tool is not that great as some other ticketing software that other organizations generally use viz., Service Now, etc. However, what I've heard from the Enterprise team at our company is the absence of the nice look and feel is complemented by its seamless command line utility admin capabilities as well as the solution's pricing. And of course, another add-on this tool is missing is the problem with any ticket's timer. For example, when a Service Desk Analyst responds to a User ticket and stalls the ticket the ticket doesn't explicitly stops the timer. This produced a problem in our Service Metrics Reporting Activity. Review collected by and hosted on G2.com.
Request Tracker is a no-frills bug tracker software used by the Perl community (the tracker at https://rt.cpan.org is used by most Perl packages on the CPAN). The tracker won't win any design awards (it's not particularly pretty, it was made by engineers for engineers) but it works reasonably well for what it does. You open bugs, add comments, subscribe others to bugs, etc. Review collected by and hosted on G2.com.
It's an older technology and lacks the sort of integration with version control systems that users come to expect.
In many cases, GitHub Issues may be a better fit (it's nice to be able to reference issues in your commits and have some basic integration between the two - e.g. "Changes foo, bar, qux. This addresses issue #42" -- the Request Tracker doesn't provide this sort of integration.
It works pretty well for what it does. Its use for basically all distributions on CPAN ensures that it can scale to a large number of projects and issues. Review collected by and hosted on G2.com.