Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 4.4.8, 4.5.4
-
Fix Version/s: 4.7.x
-
Component/s: CiviMail, Core CiviCRM
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Paid Issue Queue
-
Overview:Support Hierarchical groups in custom search and CiviMail
-
How it works currently:if you use a parent group in the Exclude field for either a CiviMail mailing or the Include / Exclude Custom Search, the contacts directly in the group are excluded but the contacts in the child group are NOT excluded.
-
How it should work:When groups are included or excluded in custom search and CiviMail recipients, both the members of those groups AND all of the members of their child groups should be included or excluded.
-
Acceptance Criteria:Test smart and static groups, and static contact on smart group. Test including and excluding. Test for custom search and for CiviMail.
Description
When you use a parent group and do a search on the parent group, the search results include the contacts directly in that group plus the contacts in the child group(s).
So, if you use that parent group in the Exclude field for either a CiviMail mailing or the Include / Exclude Custom Search, you would expect that the contacts directly in the group and the contacts in the child group would be excluded. But the contacts in the child group aren't excluded - only the contacts directly in the parent group are.
This was reported to me by a client using 4.4.8 under WordPress, where we verified it, and then I tested and verified it on the demo site using 4.5 under Drupal.
