New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed post columns when a user selects fields #3141

rowasc opened this Issue Jul 6, 2018 · 2 comments


None yet
2 participants

rowasc commented Jul 6, 2018

Describe the bug
Note: It's this way by design but we need to revisit it.
There are fields that the user cannot "unselect" from an export due to being common to all posts. (the ones highlighted here)

**Post ID **Survey **Post Status **Created (UTC) **Updated (UTC) **Post Date (UTC) **Contact ID **Contact **Sets Description Test markdown Title renamed Full Name Test Test point.lon Test varchar Categories Date of birth Missing date Geometry test Last Location Last Location (point).lat Last Location (point).lon Possible actions Second Second Point.lon Status 2

Where was the bug observed

To Reproduce
Steps to reproduce the behavior:

  1. Start an export job with only some fields of a survey selected
  2. Only the selected fields + the fixed fields highlighted (**Post ID | **Survey | **Post Status | **Created (UTC) | **Updated (UTC) | **Post Date (UTC) | **Contact ID | **Contact | **Sets ) will appear.

Verify this is expected behavior

@rowasc rowasc changed the title from FIxed post columns when a user selects fields to Fixed post columns when a user selects fields Jul 6, 2018


This comment has been minimized.


rowasc commented Jul 6, 2018

@jrtricafort this is technically not a bug, but worth checking in with you, @aoduor @Hazellaura @willdoran @Erioldoesdesign if it's something we want to keep or stop doing.
To stop doing this we would need to provide some sort of selection for those fields that clearly marks them as "common to all surveys" since we can't remove them only for some surveys and not others


This comment has been minimized.

Erioldoesdesign commented Jul 27, 2018

oh gosh 21 days ago...sorry for the delay!

From a UX POV unless being able to de-select any of those fields will fundamentally confuse and cause the user more harm/have them repeat actions/export then we should allow users full flexibility to choose what fields to export.

If we feel strongly that we should be recommending that users always export with certain fields selected we can advise and provide a default but not force.

I'm looking at CSV improvements from a UX POV this Q3 so I'll consider this in my designs for sure :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment