[MGNLPUR-80] The configuration of PUR between a new instance and a migrated instance must be the same Created: 21/Jan/13  Updated: 13/Nov/13  Resolved: 13/Aug/13

Status: Closed
Project: Magnolia Public User Registration
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.4

Type: Task Priority: Major
Reporter: Samuel Schmitt Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLMIGRATION-216 Define integration tests in order to ... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLPUR-82 Add in a version handler the delta be... Sub-task Closed Robert Šiška  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

As discussed for STK (MGNLSTK-1073), when the migration module change its logic it could happen that a new version of PUR and a migrated one dont have the same configuration.



 Comments   
Comment by Robert Šiška [ 13/Aug/13 ]

All subtasks closed.

Consistency between migrated and installed module can be checked with magnolia-migration-integration module.

Generated at Mon Feb 12 06:42:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.