[MGNLDAM-744] Enforce required fields for bulk upload of assets Created: 19/Apr/18  Updated: 22/Apr/20  Resolved: 22/Apr/20

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

Type: Bug Priority: Neutral
Reporter: Natascha Natum Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLDAM-615 Offer to specify metadata for all ass... 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: DAM improvements 2
Story Points: 8

 Description   

PXMDAM-1.1

------------------

As a Manager, I need the asset upload form fields, which we defined as required, to also be enforced during bulk (zip upload), so that necessary metadata for all assets is complete.

As an Editor, I want to include copyright and source of my assets during bulk upload so that I don't have to fill out that data for every single asset.



 Comments   
Comment by Richard Gange [ 22/Apr/20 ]

Hi,

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Best regards,

The Magnolia Support Team.

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