Getting the wrong assign_to user when creating views with assign_to filters
hgrindba - October 8, 2009 - 07:36
| Project: | Case Tracker |
| Version: | 6.x-1.0-beta4 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
We've been using Case tracker at our local workplace.intranet. It has worked great until now. I recently upgraded frrom Casetracker 6x-10-beta1 to beta4. We have created multiple projects with cases and assigned these to different users. After installing beta4 I'm not getting the correct assigned_to user when using filters created by views. For example a case assigned to userA shows up nicely with userA as assigned_to in the fields column, BUT when trying to filter for userA I end up with the assigend_to cases for UserB. This i VERY frustrating atm. Can you please look into this?
- Helge
#1
Are you using the default views provided by casetracker, or have you build your own?
If you are using your own can you attach the exported definition of one?
#2
Hi! Thx for answering. I'm using the casetracker_project_cases view as template, which I've attached som modified views. Look at the view named raditoppgaveliste. When choosing the name of the assigned user i get another users cases. The only choices that work correctly is 'any user' and 'current user'.
#3
I have similar issue, but that's what I have done:
I added a custom CCK data field "Due date" to case node then I made a new view "Outdated cases" with corresponding filters. The fun thing is ALL the cases display "Guest" as assigned user. I think these problems may be related to each other - wrong assigned user display in views with custom filters.
#4
The same issue happens with Open Atrium installation of Casetraker (6.x-1.0-beta4) - on OA's site as well.
Here's the issue, which provides more specific information -- and to cross-reference:
https://community.openatrium.com/issues/node/833#comment-2033