CRM-1687 Unexpected Behaviour assigning relationship type to memberships

          Details

          • Type: Bug
          • Status: Done/Fixed
          • Priority: Minor
          • Resolution: Won't Fix
          • Affects Version/s: 1.7
          • Fix Version/s: None
          • Component/s: CiviMember
          • Labels:
            None

            Description

            When creating a membership type with the 'relationship type' set to "Household member is", membership is granted to any individual who is listed as a "Household member of" but not to the individual listed as "Head of household for" the member household. The head of the household would presumably be the most important individual to have recorded as a member.

              Attachments

                Activity

                [CRM-1687] Unexpected Behaviour assigning relationship type to memberships
                Donald A. Lobo added a comment -

                1. relationships are not aware of each other (i.e. we dont have transitive relationships). Currently there are no special "relationship types" either. thus while WE (a human) interprets that head of household implies household member, that knowledge is not present in the relationship system (for now).

                i suspect we'll have to extend and create "special" relationship types etc when we build workflow for householding and employee/employer. At that point we'll need to address such issues. I dont think this is currently in our scope and i'd like to avoid special casing anything at this stage

                  People

                  • Assignee:
                    Donald A. Lobo
                    Reporter:
                    James Sully

                    Dates

                    • Created:
                      Updated:
                      Resolved: