[EXTDAM-338] S3 Asset status is Public/Private not Published/Unpublished Created: 19/Jan/22  Updated: 26/Aug/22

Status: Open
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Laura Delnevo Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon EXTDAM-325 Edit asset not unpublish it Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: AuthorX Maintenance
Team: AuthorX

 Description   

When S3 users work with assets, they might be familiar with S3 naming conventions and terminology. S3 assets are either Public or Private.

For Magnolia consistency (see Mgnl Assets or Pages) our statuses are changed to Published, Unpublished.

 

PM/UI investigation needed:

  • if an editor is used to S3, will he be confused by the different terminology

 


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