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

Activity Types are sorted by Component + Weight, but component column is hidden if CiviCase is not enabled

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 3.4.alpha
    • Fix Version/s: 4.1.0
    • Component/s: Core CiviCRM
    • Labels:
      None

      Description

      When CiviCase is not enabled, the ordering or activity type options is confusing because they are sorted by Component (e.g. Contact, CiviCase, CiviMember etc.) and THEN by weight, BUT the component column is not visible in the listing.

      We'll remove the logic which hides the Component column - so that it is always visible. This should make the sorting a bit more understandable.

      With regard to original post from Matt - if you click the icon to move a "Contact" related activity type to the bottom, it will be displayed at the bottom of the set of activity types that are used for Contacts (e.g. the Contact component set) - but not at the bottom of the entire list of activity types. This sort pattern makes sense since the activity types exposed to users in dropdowns are limited by component.

      — original post ----
      If you try to move around the Activities and give them different weights, it seems that the display gets broken. Basically, if you move the very last entry up one, there's never a way to move it back down.

        Attachments

        1. ActivityEntry.png
          172 kB
          Matt Burkhardt
        2. ActivityList.png
          204 kB
          Matt Burkhardt
        3. ActivityTypes.png
          147 kB
          Matt Burkhardt

          Activity

            People

            • Assignee:
              dgg David Greenberg
              Reporter:
              matthewboh Matt Burkhardt
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: