summaryrefslogtreecommitdiff
path: root/devel/rt3/patches
AgeCommit message (Collapse)AuthorFilesLines
2008-08-23Update rt3 to version 3.8.1 (from 3.6.6). Changes are:tonnerre2-14/+3
* New visual style (web2). * Rich text mails. * Email signatures and encryption. * User settings for: - Ticket history ordering. - Timezones. - Date and time format. - Username format. - Default queue. - Size of message text boxes. * Charts of ticket relationships. * Breeze through upgrades with new upgrade tools. * Subscribe to iCalendar feeds of ticket due dates. * Bookmark frequently-used tickets. * Turn off mail from RT when you go on vacation. * Get your mail from RT as a daily or weekly batch. * Delete historical or spam tickets with RT::Shredder (only as a superuser). * Set up more configurable business rules with new Scrip Conditions and Actions. * Forward tickets to third-parties from within RT. * Enable and Disable RT extensions with the new Plugins system. * Automatically log out inactive users with rt-clean-sessions. * Run faster with less memory, thanks to numerous performance improvements and bug fixes. * Fixed a potential HTML injection attck via user's properties. * Better support for installation on Solaris and FreeBSD (non-GNU make). * Updates to documentation and scripts for upgrading from MySQL 4.0 * Updated upgrade documentation for the new Queue Tag and bookmarks features. * Multiple bugs in iCal support fixed. * Backwards compatibility fixes for extensions developed against 3.6 * Added support for external links in tabs and targets. * Addition of a new callback before ticket creation so you can implement custom validation or stop creation for another reason. * Missing documentation to external authentication configuration variable in bin/rt and make it possible to set it via ENV. * Merged method in RT::Ticket.
2008-03-16Update rt to version 3.6.6tonnerre1-13/+0
Significant changes: - Reminders (remind of taking actions on an inactive bug at some point) - "Googleish" simple searches - Email input completion - Revamped theme engine - Support for UTF-8 password - Many more translations - Various Bugfixes Approved-by: cube
2007-11-13Pull up a change from 3.6.5 to support MIME-tools > 5.420.cube1-0/+13
PR#37372 by Jon Bailey. No version bump: riding the update 5 minutes ago.
2007-08-09Reap undead patches.cube3-77/+0
2006-06-03Install sbin/rt-dump-database script.seb3-0/+77
Apply fix from http://svn.bestpractical.com/cgi-bin/index.cgi/bps/revision?rev=5218 << * get rid of "masks earlier declaration" warnings >> Bump PKGREVISION to 1. Approved by MAINTAINER.
2006-05-01Update rt3 to version 3.4.5. This is _not_ an easy update, although thecube2-34/+13
changes are apparently minor to a end user (but not for the site administrator). It'd very hard and very long to provide a full list of changes. The main changes in RT 3.4 are a complete rework of how Custom Fields are handled, which means there is a lot more flexibility in that area now (including Custom Fields for users, per-queue, per-transaction). RT 3.4 is also supposed to be faster, which certainly is no bad news. Another bonus of RT 3.4 are the availability of extensions, and I will commit RTx::Shredder and RTx::RightsMatrix very soon. Updating RT is not an easy task, be sure to backup your database, and don't forget to grant the new rights to relevant people. In pkgsrc, rt3 is also seeing a few changes. The main one is the situation of the "local" path, which is now set to /var/rt3, which seems less lame to me than the previous value. It could be debated, though.
2005-09-21Mason API has changed after version 1.28. Add a patch to catch up with thecube1-0/+34
change (it breaks for callbacks). Inspired from the commit to solve the same issue on the 3.4 branch of RT. Bump PKGREVISION and Mason version requirement.
2004-08-03Initial import of rt3, version 3.2.1, into the NetBSD Packagescube1-0/+33
Collection. This package is based on the work of Dieter Roelants in pkgsrc-wip, with a lot of changes to make it proper WRT pkgsrc. RT is an industrial-grade ticketing system. It lets a group of people intelligently and efficiently manage requests submitted by a community of users. RT is used by systems administrators, customer support staffs, NOCs, developers and even marketing departments at over a thousand sites around the world.