When a content type is defined to work as a "case" by casetracker in admin/settings/casetracker and this content type is not casetracker_basic_case, actions cannot be performed in nodes of this content types.

Patch attached.

CommentFileSizeAuthor
#4 casetracker-actions-811202-4.patch8.76 KBbasvredeling
casetracker-actions.patch2.87 KBdagmar

Comments

akin.demirci’s picture

akin.demirci commented

I ran into this bug too. Not all case content types' machine name is casetracker_basic_case. Subscribing.

mrthrelfall’s picture

mrthrelfall commented

I also ran into this bug - when will the patch be rolled in to the module?

laura s’s picture

laura s commented

I tested this patch on an Open Atrium instance, but it had no effect on the ability to create actions to change case state, priority, etc.

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
commented
StatusFileSize
new casetracker-actions-811202-4.patch8.76 KB

Merged patch with #1205114: Action update by comment fails, marked 1205114 a duplicate.

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
commented

Patch is longer than necessary because line endings have been corrected automatically, but it still needs a review. Anyone?

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
commented
Title: Casetracker actions does not always work » Casetracker actions don't check for valid case types

Changed title to avoid confusion with this issue: #1803518: Casetracker actions autocomplete doesn't assign to uid