Skip to content
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

The Main medical condition and Comorbidity items in the pop-up for a subcohort are presented in random order #4287

Closed
Tracked by #4147
hslh opened this issue Sep 30, 2024 · 0 comments · Fixed by #4332

Comments

@hslh
Copy link
Contributor

hslh commented Sep 30, 2024

What version of EMX2 are you using (see footer)
v11.15.3

Describe the bug
The Main medical condition and Comorbidity items in the pop-up for a subcohort are presented in random order but should be in alphabetical/numerical order.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://emx2.dev.molgenis.org/catalogue/ssr-catalogue/all/cohorts/testCohort2#Subpopulations'
  2. Click on 'test subcohort 2A'
  3. See sections Main medical condition and Comorbidity in the popup
  4. See error

Expected behavior
The Main medical condition and Comorbidity items should be displayed in alphabetical/numerical order

Screenshots
Screenshot 2024-09-30 at 16 36 29

Desktop (please complete the following information):

  • OS: MacOS
  • Browser: Firefox 130.0.1

Additional context
The Main medical condition and Comorbidity items in the pop-up for a subcohort are presented in random order but should be in alphabetical/numerical order. Test plan 5 step 45

@hslh hslh changed the title The Main medical condition and Comorbidity items in the pop-up for a subcohort are presented in random order but should be in alphabetical/numerical order. Test plan 5 step 45 The Main medical condition and Comorbidity items in the pop-up for a subcohort are presented in random order Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant