Survey responses are not being migrated correctly when upgrading from Mifos 1.6 to 2.0
Mifos 1.6 test database is attached to this issue.
Two screenshot are also attached to this issue.
1) expected.png , at Mifos 1.6 the response is shown correctly, and same should appear after upgrading to 2.0
2) actual.png , after upgrading to Mifos 2.0 survey responses are lost (not correctly mapped) for Choice or Single select type
NOTE: This bug is related to responses only single select OR choice type of Survey (not custom fields).
So, it won't affect users who are not using Survey with Single Select OR Choice type question.
An upgrade might need to be created to fix this issue.
OR the code be fixed in the next point release of 2.0.x (2.1.x won't have this code as survey code is removed from there)
It was interesting that 100+ GB database didn't had any survey(except PPI which will be migrated externally) which we used for testing.
To be fixed based on its impact on clients. GK is unaffected by this bug.
Also decision to be taken based on whether the fix would be on e-release branch or a separate patch as this migration code is not available from f-release onwards
The data which is affected by this issue requires manual verification at database level using this query.
If you have zero rows as result then your database is NOT affected by this issue. Make sure you have applied query in correctly.
If you are affected.
The result of this query will be id(numbers) instead of response text.
STEP 1: make backup of question_group_response table. e.g.
mysqldump -u mifos -pmifos mifos question_group_response > qgr.sql
STEP 2: Run the update query to fix the data
(This query only affects question_group_response table, so if something goes wrong you can restore the question_group_response table)
STEP 3: check for mysql warnings/errors (there should NOT be any warning or error after running the query).
mysql> SHOW WARNINGS;
Added as known issue in the release notes of 2.0 and 2.1
Status has been changed to 'Won't fix' because there is no necessary to work on this ticket.
I am closing this issue. There is no need to fix this ticket, User can resolve this problem manually according to Udai's instructions.