[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Hieu Nguyen Duc Documentation update required: Yes Release notes required: Yes Account: Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Hieu Nguyen Duc 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 a an explicit role archive tasks.In 5.4.x its line 143 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:{code}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 thisif (user.getAllRoles().contains("superuser")) {addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");}{code}In 5.3.x its line 153 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:{code}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 thisif (user.getAllRoles().contains("superuser")) {addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");}{code}In my opinion, a an implementation like this is exactly what the comment says: "we hack it like this"... Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Mikaël Geljić Labels: parked support Account: Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Michael Mühlebach Sprint: Basel Saigon 43 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Michael Mühlebach Sprint: Basel 43 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Michael Mühlebach Support Score: Account: Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Jan Haderka updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Jan Haderka Fix Version/s: 5.5 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Michael Mühlebach Sprint: Basel 18 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Michael Mühlebach Sprint: Basel 17 18 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Philip Mundt updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Philip Mundt Fix Version/s: 5.4.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Michael Mühlebach Sprint: Basel 16 17 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Espen Jervidalo Labels: parked selected-for-backlog support Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Michael Mühlebach Sprint: Basel 15 16 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Jan Haderka updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Change By: Jan Haderka Sprint: Saigon 14 Basel 15 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3590) Make bulk actions configurable in the Pulse
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-3590 Make bulk actions configurable in the Pulse Nice one! It's pretty big, but it's also well split as far as I saw Just rephrased issue title, and let's make sure we have 2 reviewers. Change By: Mikaël Geljić Summary: Get rid of TODO: Let Make bulk actions configurable in the customer decide who can archive tasks and don't hardcode it ('superuser' role)! Pulse Tasks which are resolved can only be achieved by users with 'superuser' _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 a explicit role archive tasks.In 5.4.x its line 143 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:{code}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 thisif (user.getAllRoles().contains("superuser")) {addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");}{code}In 5.3.x its line 153 in info.magnolia.ui.admincentral.shellapp.pulse.item.list.PulseListFooter:{code}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 thisif (user.getAllRoles().contains("superuser")) {addRemoveMenuItem(i18n, itemsTable, contextMenu, "pages.publish.actions.archive");}{code}In my opinion, a implementation like this is exactly what the comment says: "we hack it like this"...