[MGNLDAM-771] Uploaded file name is not used when storing the asset Created: 28/Nov/18  Updated: 18/Jan/19  Resolved: 16/Jan/19

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Antti Hietala Assignee: Dai Ha
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 3.5h
Original Estimate: Not Specified
Environment:

6.0 (Snapshot: 2018.11.28 03:00:42)


Attachments: PNG File Screen Shot 2018-11-28 at 17.03.32.png     Zip Archive alternative.zip     PNG File untitled.png    
Issue Links:
duplicate
duplicates IMGREC-9 Recognise image uploaded via dialogs ... Closed
is duplicated by IMGREC-37 New assets are saved without names Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Resurface finalisation
Sprint: Features 2, Features 3
Story Points: 0.5

 Description   

Assets app discards the uploaded asset's file name. The file name should be used as asset name in JCR. The resulting asset is wrongly named as "untitled".

To reproduce:

  1. Upload an image to DAM.
  2. Observe the resulting asset name in JCR. Should be the same as the file name.

Impact: Having to rename the asset manually after upload is redundant. It slows the user down and is annoying. 

Regression in 6.0 compared to 5.7.1 behavior.



 Comments   
Comment by Dai Ha [ 09/Jan/19 ]

Regression due to decoration of image-recognition action, PR in IMGREC-9 will remove that decoration part and thus, fix this issue.

Comment by Dai Ha [ 10/Jan/19 ]

Attach of my alternative work in alternative.zip

Comment by Hieu Nguyen Duc [ 16/Jan/19 ]

It has been fIxed in IMGREC-9.

Generated at Mon Feb 12 05:03:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.