[EXTDAM-344] S3: The parent item should always be the 1st element Created: 22/Feb/22  Updated: 24/Feb/22  Resolved: 24/Feb/22

Status: Closed
Project: External DAMs
Component/s: s3
Affects Version/s: 1.1.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Jesus Alonso Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2022-02-22-15-41-16-934.png     PNG File image-2022-02-22-15-41-49-642.png    
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)
Epic Link: Extdam Later
Story Points: 2

 Description   

Steps to reproduce

  1. Login in Magnolia
  2. Go to S3 assets
  3. Go inside a bucket
  4. Click on some header (e.g. name) to order the list by that attribute

Actual results

The parent element is not the 1st element anymore (it is ordered) and so, if you have several elements, you won't see how to go to the parent folder.

Expected results

The parent element is always the 1st element



 Comments   
Comment by Jesus Alonso [ 24/Feb/22 ]

It turns out it is not possible to order s3 assets. See EXTDAM-345

Generated at Mon Feb 12 01:54:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.