Posted by imp7 on October 5, 2009 at 3:23am
| Project: | Case Tracker |
| Version: | master |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I love the simplicity of Case Tracker, but when you create a case for a project management things become more complicated.
My thinking is that for a case to be resolved there are usually a series of tasks that need to be resolved first.
In this issue tracker in drupal it seems to be done through pages and pages of comments. I am wondering however if a hierarchical reference structure would ever be in the scope of this module?
I am aware of other modules like storm with this type of functionality, but the simplicity of case tracker to build upon, is what I am after.
Cheers :)
Comments
#1
It's possible that something like this map be possible with casetracker.... someday. In the 1.x branch we won't be doing this. I'm experimenting with a radically different structure for casetracker (here http://github.com/miccolis/casetracker in case you want to follow along) which would make this possible but I can't say when (and if really) it'll become part of the official casetracker project.
#2
I've thrown together something based on CCK that works for me on the 1.x line: http://grayside.org/2009/11/casetracker-subtasks. Most of the connection with Case Tracker is in the theme override.
#3
Bah, upload on initial post only...
#4
Hi. Please is there a plan to roll this into the official version ?
#5
Unfortunately not. This functionality might exist in the future as part of Case Tracker 2. The tarball above is a CCK-based system which has a slim chance of a slight upgrade and becoming a barely supported Feature Module available on a site other than D.O.
You might be able to fund jmiccolis to expedite CT2 and prioritize subcases.