Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-7787

Allow for same term in different tagsets

    Details

    • Type: Improvement
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Won't Fix
    • Affects Version/s: 3.3.5, 3.4.4, 4.0.4
    • Fix Version/s: 4.4.0
    • Component/s: Core CiviCRM
    • Labels:
      None

      Description

      Currently it is impossible to add a tag with a duplicate term in the name across different tagsets. Example:

      Tagset:
      Political Interests
      With Terms:
      Education
      Youth
      Human Rights

      Tagset:
      Works in
      With Terms:
      K-12
      Education <--- THIS IS NOT POSSIBLE - because the term 'Education' is already used in previous Tagset

      Tagsets should have unique terms within each tagset, but should not be impacted by other tagsets, so we should be able to have the term 'Education' in both tagsets.

      Some considerations:

      Terms outside of tagsets - should be unique, and we need to make sure that we are still checking that after making changes.

      Currently there is a uniqueness constraint in the DB for tag names - this will need to be addressed, and we'll need to coordinate to get the upgrade script to make adjustments..

        Attachments

        1. civicrm_tag.name.not.unique.sql
          0.1 kB
          Mike Chelen
        2. civicrm_tag.UI_name_parent_id.sql
          0.1 kB
          Joe Murray
        3. tag.allow.duplicate.patch
          0.3 kB
          Mike Chelen
        4. tag.unique.tagset.2.patch
          2 kB
          Mike Chelen
        5. tag.unique.tagset.patch
          2 kB
          Mike Chelen

          Activity

            People

            • Assignee:
              kurund Kurund Jalmi
              Reporter:
              queue kyle jaster
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: