[CONTTAGS-106] New asset name not filled correctly Created: 18/Dec/20  Updated: 01/Feb/21  Resolved: 28/Jan/21

Status: Closed
Project: Content Tags
Component/s: None
Affects Version/s: 2.0.2
Fix Version/s: 2.0.3

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1h 13m
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDAM-919 Asset names are different in the Asse... Closed
causality
duplicate
duplicates MGNLDAM-875 Upload assets create untitled nodes r... Closed
is duplicated by MGNLDAM-919 Asset names are different in the Asse... 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
Epic Link: Migrate Assets
Sprint: UI FW 20
Story Points: 5

 Description   

Steps to reproduce

  1.  Upload a new asset using upload asset action
  2.  Fill name field
  3. Upload new asset
  4. Go to jcr browser to check the new asset node name

 

Expected results

The asset node name must be the given name in the form when filling the field or the name of the uploaded file

Actual results

Untitled is set as node name. This is confusing when it comes to perform searches within the assets tree view

Workaround

For the problem with asset searches, add a column referencing the property name instead of jcrname

Development notes

In info.magnolia.dam.app.action.JcrAssetCommitAction.write(), when checking if item is new, item.isNew(), it returns false so the logic to assign a proper name is never executed.


Generated at Mon Feb 12 00:25:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.