Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-3590

Make bulk actions configurable in the Pulse

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: 5.3.10, 5.4.2
    • Fix Version/s: 5.5
    • Component/s: pulse
    • Labels:
    • Release notes required:
      Yes
    • Documentation update required:
      Yes
    • Sprint:
      Saigon 43
    • Story Points:
      8
    • Magnolia Release:
      5.5

      Description

      Tasks which are resolved can only be achieved by users with superuser role.
      But this does not fit reality in projects...
      The customer needs to be able to decide, who can archive successful pulse tasks.
      It is a 'no go' to give somebody complete superuser rights just to be able to archive pulse tasks.

      A valid situation would be:

      • Let also publishers archive their tasks.
      • Or, let an explicit role archive tasks.

      In 5.4.x its line 143 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:

      User user = MgnlContext.getUser();
              // TODO ideally context menu action availability should use the same mechanism and rules defined in the messageView config
              // but as this is not straightforward, for the time being we hack it like this
              if (user.getAllRoles().contains("superuser")) {
                  addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");
              }
      

      In 5.3.x its line 153 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:

      User user = MgnlContext.getUser();
              // TODO ideally context menu action availability should use the same mechanism and rules defined in the messageView config
              // but as this is not straightforward, for the time being we hack it like this
              if (user.getAllRoles().contains("superuser")) {
                  addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");
              }
      

      In my opinion, an implementation like this is exactly what the comment says: "we hack it like this"...

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sang.ngo Sang Ngo Huu
                Reporter:
                cringele Christian Ringele
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3d Original Estimate - 3d
                  3d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 6.5d
                  6.5d