We use it for:
Customer Support (product issues)
IT Helpdesk (internal)
Service Requests
Projects
Software Issue Tracking (internal)
Corrective and Preventative Actions (QMS)
Document Changes (QMS, basic integration with SVN)
Nonconforming Products (QMS)
Taan
___
On May 14, 2007, at 2:15 PM, Teresa Carcelén Fernández wrote:
Thanks a lot, specially to Mark and Jesse.
Yes, It´d be a good idea to include this advantages in the RT wiki
Wikis are designed to allow the community to add content. I'd be
indebted if you could add what you've learned there.
Thanks a lot, specially to Mark and Jesse.
Yes, It´d be a good idea to include this advantages in the RT wiki
I´m amazing how cool is RT. And now AT, wow.
Please, I have the last question, RT is not made for Bug Tracking System,
isn´t it?
Best Regards
Teresa
2007/5/14, Matthew Keller <[EMAIL
I REALLY wish these things were listed in the RT wiki.
Wow. That looks great.
On Mon, 2007-05-14 at 13:19 -0400, Jesse Vincent wrote:
> >
> >> software development
> >
> > We have custom fields in development queues for things like "Revision
> > Version" and "Code Status", and tie this in with S
software development
We have custom fields in development queues for things like "Revision
Version" and "Code Status", and tie this in with SVN (Subversion) to
allow for very fluid tracking of development items. You'd need to
put in
some custom legwork to make this really snap, but it works
On Mon, 2007-05-14 at 18:00 +0200, Teresa Carcelén Fernández wrote:
> Can anyone tell me some examples where RT can be applied for ?
>
> 1. project management
We use RT extensively for project management. Parent/child and
dependency functionality makes this very nice. Also, when using
extension
Hi all!
Can anyone tell me some examples where RT can be applied for ?
1. project management
2. help desk,
3. NOC ticketing. Basically, this is what it is made for.
4. CRM and software development
Thanks in advance
Best Regards
Teresa
___
http://l
