[MGNLDAM-339] Make sure configuration between migrated and fresh instance is the same Created: 14/Nov/13  Updated: 20/Nov/13  Resolved: 20/Nov/13

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

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Jaroslav Simak
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLDAM-334 Remove dms bypasses filter definition 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: Enable 4.5 to 5.x upgrade
Sprint: 5.2-rc2

 Description   

1/server/filters/servlets/DamDownloadServet/mappings/dms-* should be removed when updating from Magnolia 4.5.x.
Diff report:
http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/server.filters.html


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