Releases for Case Tracker

Major code refactoring

• Move toward a more OO approach, using more of what Entity API provides
• Make it easier to to extend the module (evolutions needed while working with the Scrum module - http://drupal.org/project/scrum).
• Cleanup and reorganize some code pieces to make it easier to find and maintain the module

UX improvements

• Everything is under /projects path now, avoiding some weird behaviours occurred while under /admin

the initial port of case tracker module for D7. Enabling this release for
1. more broad testing
2. localize.drupal.org translation

This release is the first one with a working version of Case Tracker for Drupal 7. You can create Projects and Cases without problems, but the 2 submodules, Notifications and Actions, aren't tested. It seems that all Views are fully working, but needs more testing.

Bug fix release of Case Tracker for Drupal 6.x

• Properly santizing output on the casetracker admin screens.
• Proper token handling for status updates, patch by dagmar.
• Properly escaping status/type/priority names when displaying. Bug reported by dagmar.

This is mostly a bug fix release, but with a few important changes.

The always confusing `access case tracker` permission has been removed. This permission was nearly always misinterpreted as a node access style setting. It could prevent users from seeing certain displays, but not from seeing the nodes themselves. Users who relied on this permission are advised to reconfigure the default Views provided by casetracker to use an access plugins which checks the current users role.

The `casetracker_mail` module has been removed. This module never got the full D6 upgrade that it needed. Many users have already transitioned to using the Notifications and Messaging modules which can be use to replace most (if not all) of the outgoing mail functions that had been provided by `casetracker_mail`. This is now the recommended approach. We'll probably add a re-concepted `casetracker_notifications` module in the future to strengthen this integration.

Other changes in this release include:

• Updated the README.txt
• Removing the 'access case tracker' permission.
• #759434 by dagmar, Assign to user widget more configurable
• #759566 by dagmar, Make "assigned to" a view relationship.

Beta 5 Release of Case Tracker for Drupal 6.x
-------------------

Various fixed and Changes, including:

Bug fixes and improvements, including:

* Using views to control which users can be assigned cases.
* More consistent exposed filter forms
* bringing back the 'Jump to case' block.
* Improved handling of case meta-data on node preview.

Beta release of Casetracker for Drupal 6.

Second beta release of the 1.3 branch. Contains many small bug fixes.

Warning!

There is a bug in the install (only for new casetracker installs) script!
If you install this version (fresh install) then you have to manually run the update.php script and select the update #21 from the casetracker module dropdown.

Or you can use the casetracker 5.x-1.3-beta1 release instead!

New features

Organic Groups support

The Case Tracker module supports now Organic groups:

This is an intermediate release.

It has some bugs fixed and some new features many people asked for.

It has been tested by a limited group of users, it is pretty stable but still has some known bugs

 * hook_uninstall() has been added to basic, core, and mail.
 * basic node types renamed: casetracker_basic now ships with node types named
   casetracker_basic_project (and _case) as opposed to the original form of
   casetracker_project. this renaming was a paranoid sideeffect of adding a
   hook_uninstall() which would DELETE node types named casetracker_project.
   we felt that such a name would be relatively common for custom CCK-like
   installations, and didn't want to see accidental deletions when and if

A final (save for important bug fixes) version for Drupal 4.7, entirely reworked by Morbus Iff.

 * database: casetracker_comment merged with casetracker_comment_status.
 * all css ids and classes are now - delimited, not _.
 * database: casetracker_case:p_id is renamed to pid.
 * database: casetracker_case:case_id is renamed to case_number.
 * database: casetracker_comment_status:project_term_id renamed to pid.
 * database: casetracker_project:project_no is renamed to project_number.
 * casetracker > cases menu item is now modifiable. hackish, but ok.
 * casetracker_case_state_load() now issues one query and then caches.
 * mail sending and receiving has been moved into casetracker_mail.module.
 * Removed the use of sequences to keep track of Case Tracker's project and
   case numbers. The sequences for cases were never implemented properly; to
   do them right would mean filling up sequences with a per-project counter.
   Everything has been moved to a settings variable which, while allowing for
   a race condition, doesn't abuse sequences (with both amount of project
   case numbers and the forcing of +100 instead of +1 by db_next_id()).
 * "Jump to case number" block now requires 'access case tracker' perms.
 * "Latest cases" block configuration moved to block edit screen.
 * xmlrpc_example.php added to repository, demonstrating simple client access.