Future feature requests


#1

After using RT for a little while, naturally, I’ve thought of a few ways
that would benefit its use in my environment.

  • I think I’ve seen these before:

    • Having a scrip event onOwnerChange
    • A scrip event based on when a ticket enters a queue from another
      queue.
  • More of a long-term idea:

    • Ability to click on a link in any given correspondence and turn
      corresp. into a knowledgebase type article. This would maybe insert the
      specific comment/correspondence into a separate knowledgebase table that
      would contain various articles.

I’m interested in hearing anybody’s thoughts. Also, is there an easy way to
learn how to create custom scrips?

Thanks,
Eric Mandel


#2

Eric Mandel EMandel@worldnow.com writes:

After using RT for a little while, naturally, I’ve thought of a few ways
that would benefit its use in my environment.

  • I think I’ve seen these before:
    • Having a scrip event onOwnerChange
    • A scrip event based on when a ticket enters a queue from another
      queue.

Yes. I want that to.

  • More of a long-term idea:
    • Ability to click on a link in any given correspondence and turn
      corresp. into a knowledgebase type article. This would maybe insert the
      specific comment/correspondence into a separate knowledgebase table that
      would contain various articles.

This would be done in a knowledge base. Don’t try to make RT do
everything. But make it easy to connect it to all these other things,
like customer database, project, database, calendars, and more.

Maby I should mention my crazy project also… I’m trying to do a
general RDF application framework for linking all sorts of stuff,
including tickets.
http://uxn.nu/wraf/

/ Jonas - http://jonas.liljegren.org/myself/en/index.html