feature: Reports fields rename (M2-8268)

[andrevitalb]

• Tests for the changes have been
• Delivered the fix or feature branches into develop or release branches via Squash and Merge (to keep clean history)

📝 Description

🔗 Jira Ticket M2-8268

Renaming & reordering for both report.csv and activity_user_journey.csv fields. Also, renamed report.csv to responses.csv.

All these changes were added behind a workspace-wide feature flag, so won't be directly enabled by default.

Current expected columns & order (for report.csv)

id
activity_flow_submission_id
activity_scheduled_time
activity_start_time
activity_end_time
flag
secret_user_id
userId
source_user_subject_id
source_user_secret_id
source_user_nickname
source_user_relation
source_user_tag
target_user_subject_id
target_user_secret_id
target_user_nickname
target_user_tag
input_user_subject_id
input_user_secret_id
input_user_nickname
activity_id
activity_name
activity_flow_id
activity_flow_name
item
response
prompt
options
version
rawScore
reviewing_id
schedule_id
timezone_offset
legacy_user_id

New expected columns & order

target_id
target_secret_id
target_nickname
target_tag
source_id
source_secret_id
source_nickname
source_tag
source_relation
input_id
input_secret_id
input_nickname
userId
secret_user_id
legacy_user_id
applet_version
activity_flow_id
activity_flow_name
activity_flow_submission_id
activity_id
activity_name
activity_submission_id
activity_start_time
activity_end_time
activity_schedule_id
activity_schedule_start_time
utc_timezone_offset
activity_submission_review_id
item_id
item_name
item_prompt
item_response_options
item_response
item_response_status
rawScore

The changes get propagated to activity_user_journey.csv. Additional fields for said report were left unchanged.

🪤 Peer Testing

In order to test functionality, set enableDataExportRenaming feature flag to true.

✏️ Notes

Something to keep in mind is that changes to subscales will come in a separate ticket, under the same feature flag that was used for all the changes added here

[aws-amplify-us-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2002.d19gtpld8yi51u.amplifyapp.com

[felipeMetaLab]

Disabling eslint and TS

[felipeMetaLab]

Is there any reason for disabling the eslint and TS here ?
Why is it necessary?
Is there a way to make it work without forcing the bypass?

[andrevitalb]

This replicates pre-existing behavior for tests. The effort required to make the corresponding updates to remove these comments exceeds this ticket's scope. We could explore the option of making the corresponding updates to these tests at a later stage

[felipeMetaLab]

Beside the comment to disable Ts and eslint the code looks good for me.