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:
In 5.3.x its line 153 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:
In my opinion, an implementation like this is exactly what the comment says: "we hack it like this"...