[MGNLUI-3606] Batch actions for publishing, duplicating, exporting, downloading, renaming items Created: 30/Apr/15  Updated: 25/Jan/22  Resolved: 08/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: actionbar, user interaction
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Obsolete Votes: 3
Labels: ux-pain-points
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
dependency
depends upon MGNLUI-3398 Redesign action capabilities: multi-i... Closed
duplicate
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

We currently offer only a very limited set of batch actions. As far as I know they are:

  • delete items
  • move items

Commonly requested batch actions are:

  • publish/unpublish items
  • duplicate items (and copy items, once we provide it)
  • renaming items (take name, add suffix to it)
  • export items
  • download items

An additional, powerful batch action would allow us to bulk change ("edit") items. However, such a function requires more UI work: bulk changing of items is really well done in web apps such as JIRA, but those type of mass changing of items require solid UI research and powerful backend functions. Very desirable, but probably not part of this issue.



 Comments   
Comment by Christopher Zimmermann [ 24/Sep/15 ]

Would be nice to have some details here. What is still missing?

Comment by Andreas Weder [ 24/Sep/15 ]

czimmermann I've added a description with more details about which requests I had in mind when I created this issue.

Comment by Aleksandr Pchelintcev [ 28/Sep/15 ]

Imo that's a real pain point not only from UX perspective but from UI architecture entirely: it's super not straightforward to create/deal with multi-item actions from Java perspective.

Comment by Mikaël Geljić [ 30/Sep/15 ]

Same as Sasha said. I wouldn't go and waste time streamlining this across our vastly heterogeneous apps. Rather 1. improve those actions for good and 2. simplify configuration.

Comment by Christopher Zimmermann [ 27/Jun/16 ]

mgeljic Would you say this ticket could be well addressed after https://jira.magnolia-cms.com/browse/MGNLUI-3398 is resolved?

Comment by Aleksandr Pchelintcev [ 27/Jun/16 ]

czimmermann yes, the MGNLUI-3398 is definitely a preliminary requirement for the efforts targeting issues like this one.

Generated at Mon Feb 12 09:08:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.