Question

This is not a duplicate of Why is FogBugz telling me “Cannot add case”? - even if it is quite similar.

Lets say I have set up a list filter which lists cases from Project A, ordered by milestones. Below each milestone line I can not add a case with the "Add Case" - so far everything is as expected.

Now lets assume that I want to exclude a milestone from my view. This is only possible with a "-FixFor:MilestoneName" search string, since the built-in Milestone filter only allows to choose a specific milestone to show, but not the other way around.

However, as soon as there is data in the search string, the "Add Case" is disabled. So (ignoring implementation details), it is obvious that the behavior should remain the same as before; there is not less information available to FogBugz in order to perform the quick add.

This is a general problem; as long as only axis are used, the information available to add a new case is quite often unambiguous. For instance, another use case is to add a "assignedto:me" (which works for all users if the filter is shared, in contrast to the built-in Assigned To filter criteria), where it is clear that the new case must be assigned to me.

Therefore it would feel "natural" that the search axis is handled just like a normal criteria where applicable, and that this doesn't block the addition of new cases.

Answer 1

It would be great if we could parse that search string and be sure that we could still add a case that conformed to the filter, but the free form search string makes that difficult. For now, if you add a search, Add Case will always be disabled.

Answer 2

We find this to be frustrating our users as well. We solved the problem of assigning cases to multiple users using the tag everyone hack described here. Then we solved the problem of including the "everyone" cases in the "my cases" filter by creating a shared filter which searches for assignedto:userA OR (assignedto:everyonevirtualuser AND tag:userA) and requiring that everyone modify it for themselves a la the answer from here. All this only to be frustrated by this quick-add problem, even if the filter is sorted by project. Please do either rehash the search parser or change what is required to use quick-add.