Get rid of redundancy in membership applications
Closed, ResolvedPublic3 Story Points

Description

Currently, (at least in some cases) the membership application's data field contains redundant personal data that is also stored in its dedicated table column. We need to figure out, if this is used somewhere (displaying lists of data set, data export), and get rid of the redundancy.

Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptJun 10 2016, 4:05 PM
kai.nissen triaged this task as "Normal" priority.Jun 10 2016, 4:05 PM
kai.nissen set the point value for this task to 3.
kai.nissen moved this task from Backlog to New-Stuff on the WMDE-Fundraising-Frontend-Release board.
kai.nissen moved this task from Incoming to WMDE Fundraising on the TCB-Team board.

Obviously, the field request.data is not even touched during the export of membership applications. It seems, that we are good to just remove the redundancy.

Tobi_WMDE_SW closed this task as "Resolved".Apr 7 2017, 11:25 AM
Tobi_WMDE_SW claimed this task.
Restricted Application added a project: WMDE-Fun-Team. · View Herald TranscriptApr 7 2017, 11:25 AM