Posted by Jax on December 15, 2007 at 11:23am
| Project: | Case Tracker |
| Version: | master |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Currently there are 3 realms: status, priority and type. It would be nice if it's possible to add/rename realms and have the values for those realms editable when adding a comment so that the transitions are tracked.
A use case for this is that I would like another realm which is "deadline status" with values like "on track", "endangered", "management intervention required" or something like that.
Ideally you would be able to add any CCK thingy to a Case and be able to state of it should be "tracked". If it can be "tracked" you can edit the value while adding a comment. Maybe I should put this in a separate feature request.
Comments
#1
Another business case for this: A realm for "Severity" is common for customers submitting cases (Priority is for internal prioritization).
#2
another business case:
I would like to have a realm for "marketing and sales questions" this way we can use one help desk to answer product, and sales questions. this makes it easier to track the items that a customer has asked about.
#3
is anybody working on this? I'm thinking about implementing this for a project i'm working on.
#4
I'm working on this, I should have something for people to look at in the next few days. i've uploaded a patch of what I've done so far so you can get an idea of where I'm going with this. It's not done, and there's a bunch of debugging crap in it, so be wary.
#5
Subscribing
#6
has there been an update in the last 5 months?
#7
We came across this question recently. How about using taxonomy as realms which would be the drupal way and very flexible. You just would need to attach vocabularies to casetracker. What do you think?
cheers, Ronald
#8
I've also thought about switching out of custom system for taxonomy - potentially getting translation capabilities for free even.
I have not had the time to look into what that implementation would be like. If anyone else does I'd appreciate it.
#9
Maybe we could make use of this module http://drupal.org/project/comment_alter_taxonomy
#10
Subscribing.
Using Taxonomy seems to make lots of sense.
#11
FYI I've got a little experiment going here http://github.com/miccolis/casetracker It's not even testable yet, but if you're a programmer it may be work a look. It's the start of an implementation of a pluggable state system.
#12
I would prefer a CCK solution over using taxonomy. That way, one could implement a date field for deadlines.
#13
IMO, In order to conserve the performance of this module, realms should be only storaged in one table like casetracker does at this moment. If not, casetracker may be replaced by cck + comment_cck but a new node revision would be created for each change of status.
The solution for dynamic realms should be something that allow us to get the status of a case fetching a single row in a table, like project module does.
#14
when asked a user why he was using casetracker with comment_driven altogether,
and if it wouldn't be better to open a feature request for casetracker (#768202-2: Compatibility with casetracker),
he answered that it was attempted to be addressed by cckasetracker, which was discontinued in favor of comment_cck and now comment_cck is discontinued itself (#768202-6: Compatibility with casetracker)
now I found this issue, which seems to be that feature request for casetracker
and suggested alternatives are:
taxonomy - comment_alter_taxonomy (#9)
CCK - comment_cck (#12)
casetracker's own (#13)
I would like to have some thoughts from the maintainer of this module,
to have an idea regarding where casetracker is headed to
#15
Well, this request seems to be forgotten.
Its something i really needed in OpenAtrium.