When one looks at http://domain/casetracker/cases/all/assigned:0 it shows "all projects, my assigned cases.". I would expect this to show the unassigned ones. Does anyone know how to show the unassigned ones?

CommentFileSizeAuthor
#5 casetracker_4.patch464 bytesjax

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

You can create a view with the assigned to filter set to "Assigned to: Is None of: " and then select all the users on your system.

If it were up to me, I wouldn't include this filtering ability in the casetracker module itself because it can be created so easily in views. I think using the views filtering/sorting capability makes more sense than building a module specific filtering system. So, marking this as "won't fix" would make sense to me, but I leave that decision to the module maintainers and the issue submitter.

jax’s picture

jax commented

Your approach implies that the view has to be updated every time you create a new user, right? That doesn't make much sense, does it?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

That is true. As to whether or not its viable - that depends on the frequency of adding new users.

Another solution (one we use) is for all new issues to be assigned to a dummy user. Then a view for that user would always work to find the issue.

All the same, I'd like to see this solved via views (e.g. providing a new filter in casetracker_views.inc) rather than custom listing code in casetracker.

jax’s picture

jax commented

Is there a reason that 0 cannot be unassigned in stead of mine?

jax’s picture

jax commented
Title: How to view unassigned cases » Assigned:0 doesn't work.
Component: User interface » Code
Category: feature » bug
Status: Active » Needs review
StatusFileSize
new casetracker_4.patch464 bytes

Actually the problem is a bug. The code that handles the filters starts with:

if ($case_filter[1]) {

This resolves to FALSE when $case_filter[1] equals "0" which is why you cannot select the user 0. The patch changes this to isset().

Christefano-oldaccount’s picture

Christefano-oldaccount commented
Status: Needs review » Reviewed & tested by the community

Thanks, Jax. Looks good to me.

zero2one’s picture

zero2one commented
Status: Reviewed & tested by the community » Fixed

Is in the dev release, will be in the next official (> 1.2) release

zero2one’s picture

zero2one commented

Is fixed in the casetracker 5.x-1.3-beta1 release.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.