Closed (fixed)
Project:
Case Tracker
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
3 Aug 2009 at 15:33 UTC
Updated:
5 Mar 2011 at 22:11 UTC
Jump to comment: Most recent file
The new actions in case tracker allow administrative users to make changes in "invisible mode". This changes the database without posting a comment or creating a revision and thus makes it impossible to trace how a issue ended up in the current state.
I think this functionality is problematic, and should be removed.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 538830_invisibility-removed.patch | 7.26 KB | Grayside |
Comments
Comment #1
Grayside commentedI'll try to tackle this in the couple weeks.
Comment #2
Grayside commentedHere's invisibility removed.
Comment #3
jmiccolis commentedThanks for the patch, sorry for the delay. Committed!
Comment #5
akin.demirci commentedSo the invisible mode is removed. OK but which code performs the action defined in rules now? As far as I could see the only action that is performed when the rule is triggered is to insert a new comment, but no change is made to the case itself.
For example I want a case to be auto-assigned to a user according to the taxonomy term which the case updated belongs to. I set the rule, it is triggered, the comment is there, the message "Case #1617: assign_to set to 96" is there, but the assign_to field of the case #1617 in the database is not changed, still anonymous.
I am surely missing something here but what?
Thanks...
Comment #6
akin.demirci commentedSo the invisible mode is removed. OK but which code performs the action defined in rules now? As far as I could see the only action that is performed when the rule is triggered is to insert a new comment, but no change is made to the case itself.
For example I want a case to be auto-assigned to a user according to the taxonomy term which the case updated belongs to. I set the rule, it is triggered, the comment is there, the message "Case #1617: assign_to set to 96" is there, but the assign_to field of the case #1617 in the database is not changed, still anonymous.
I am surely missing something here but what?
Thanks...
Comment #7
akin.demirci commentedSorry to bother you :(
I realized what I was missing: drupal_write_record in the hook_comment.
Learning more everyday :)