[rt-users] RT 4

Scott T. Hildreth shildret at scotth.emsphone.com
Tue May 1 16:10:27 EDT 2007


On Tue, 2007-05-01 at 12:18 -0700, Justin Brodley wrote:
> I'd like to see the following:
> 
> 1. Better Documentation and resources for the product (current methods
> are cumbersome and slow ie. List Archives or the Wiki)
> 2. Ruby on rails would be great... 

     Just curious, why ror.  I would be that RT4 would be written 
     using Jifty.

> but as your PERL guys I assume
> unrealistic.  Really a complete SOA architecture would be fantastic
> 3. More complexity around Custom Fields, current model is very
> cumbersome  
> 4. Have every function and feature exported into a fully functional API
> layer  
> 5. Ability for RT to natively sync data between multiple RT instances
> (Enterprise feature set)
> 6. A robust change management interface that follows ITIL standards
> 7. Way to track SLA's based on Response and remedy commitments
> 8. Ability to do more site maintenance tasks in the GUI, DB backups, RTx
> Extensions, Simple Branding, etc. 
> 9. Reporting layer utilizing the Jasper Framework 
> 
> 
> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Jesse
> Vincent
> Sent: Tuesday, May 01, 2007 10:55 AM
> To: RT Users
> Subject: [rt-users] RT 4
> 
> If, for the sake of argument, Best Practical were to rewrite RT, what
> would you want to see in the new product?
> 
> Think big.
> 
> Jesse
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com
> 
-- 
Scott T. Hildreth <shildret at scotth.emsphone.com>



More information about the rt-users mailing list