You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new feature for mapping gender was recently added to the importer (PR #2401). The feature mimics how other features allow values to be mapped to tags, organizations or enum fields. But unlike tags or organizations, it should not be possible to import multiple genders to a single person, which it currently is.
The dropdown should contain lots of options, some of which should be disabled because they have already been configured. The Gender field should be one of the disabled fields.
Actual Behaviour
The dropdown contains lots of options, some of which are disabled, but the gender field is not one of the disabled fields.
Screenshots (if you have any)
Configuring gender (Step 8)
The dropdown with Gender enabled (step 10)
The text was updated successfully, but these errors were encountered:
Description
A new feature for mapping gender was recently added to the importer (PR #2401). The feature mimics how other features allow values to be mapped to tags, organizations or enum fields. But unlike tags or organizations, it should not be possible to import multiple genders to a single person, which it currently is.
Steps to reproduce
Sample file (CSV)
Expected Behaviour
The dropdown should contain lots of options, some of which should be disabled because they have already been configured. The Gender field should be one of the disabled fields.
Actual Behaviour
The dropdown contains lots of options, some of which are disabled, but the gender field is not one of the disabled fields.
Screenshots (if you have any)
Configuring gender (Step 8)
The dropdown with Gender enabled (step 10)
The text was updated successfully, but these errors were encountered: