ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
AAJ does not create journals, when models are created using sub classes (Bug #708)
In chiliproject_backlogs, we are using custom subclasses of the
Issue model. The subclasses contain some custom behavior, that is used in the plugin's code. This way we do not need to add them to the global
Issue model. Also, we can have different behavior for Stories, Tasks and Impediments.
This worked fine, when using Chili 1.x. With the introduction of
acts_as_journalized, we were running into a problem. AAJ derives the Journal class' name from the instance's class name. This will not work correctly, when dealing with the instances of subclasses.
The code within the pull request, that will be attached, changes AAJ, so that only models, with direct calls to
acts_as_journalized have Journal classes. All subclasses, that do not call
acts_as_journalized directly, will use their parent class' one.
[#708] Using instance var to store journal class name
this way journal classes are only created for classes with
calls to acts_as_journalized. You may now subclass journaled models to extend them with helper methods in plugins w/o interfering with aaj.
The bug results in an error message printed to standard out and the journal will silently not be created. This is handled by L134 in aaj/lib/redmine/acts/journalized/creation.rb
The pull request may be found at https://github.com/chiliproject/chiliproject/pull/125.
We would love to see this in the core, since only then people could start using chiliproject_backlogs without the need to patch the core.
- Assignee deleted (
- Status changed from Open to Ready for review