REDMINE – 7.x-1.0-beta2
Just after a few days of development work on a small Drupal installation, I was able to rebuild a good portion of basic functionality from a popular task management web application into Drupal. For me, it was stable enough to drop the usage of Ruby-based Redmine and instead host the task management software on the same platform I am developing my projects in for work. A win/win, in my book.
However, in the days following the initial development, I ran into additional edge cases to which I needed to continue development. And because the subsequent changes appear to have slowed down, I thought an update was in order.
Introducing the Beta 2 release of REDMINE (Really Extendible Drupal Modular Interface for New-task Efforts).
- Rules have been adjusted to take into account node changes, in addition to node creation.
- Additional UI elements (buttons for adding/editing content) has been added to projects, tasks, and updates.
- A default theme has been added to present how the Feature works with the appropriate CSS. Please note the theme is dependent on Zen.
- Tweaks and adjustments to the views to maximize customization.
My goals with this release were to dive a little bit more into the Reverse aspect of Views and node referencing. The Reverse function allows you to collectively display (and group) nodes which reference a particular node type.
This has proven to be a most-valuable asset, as a majority of my workflows work in a linear unidirectional format. In this case, a (1) project has multiple (n) tasks, which have multiple (m) updates.
This Reverse functionality allows me to extrapolate the project fields without having a direct reference in the Update node type.
I should note that this feature also works in Rules, but it is a bit more tricky to pull off. However, it is being solidly used, as the Rules for processing the update content type are generating redirection URLs based on the node IDs (nids) of both the project and task.