[MAGNOLIA-7238] Ability to filter metadata properties when exporting JCR bootstrap file Created: 11/Jan/18  Updated: 19/Aug/22  Resolved: 19/Aug/22

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

Type: Improvement Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-6683 Offer YAML as alternative format for ... 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)
Release notes required:
Yes
Documentation update required:
Yes

 Description   

MAGNOLIA-6683 added ability to export via YAML and to configure properties to be filtered out when exporting JCR to either XML or YAML.

The UX should offer an additional option to remove additional system properties in the interest of creating cleaner, easier to work with bootstrap files.

To specify: exactly which options should be available to a user.
There should only be a few, easy to understand options - not a list of every property.
See conversation here: https://jira.magnolia-cms.com/browse/MAGNOLIA-6683?focusedCommentId=141911&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-141911


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