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

Some data items under section 'Access conditions' in Cohort view are not shown or need to be renamed #3600

Closed
BrendaHijmans opened this issue Apr 4, 2024 · 0 comments · Fixed by #3761

Comments

@BrendaHijmans
Copy link
Contributor

What version of EMX2 are you using (see footer)
v10.49.7

Describe the bug
Some data items under section 'Access conditions' in Cohort view are not shown or need to be renamed

Fields not shown:
-data use conditions
-data access fee
-release type

Fields to be renamed:
conditions > data access conditions

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://emx2.test.molgenis.org'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@esthervanenckevort esthervanenckevort added this to the Inbox milestone Apr 19, 2024
@esthervanenckevort esthervanenckevort modified the milestones: Inbox, Sprint 221 May 3, 2024
@connoratrug connoratrug self-assigned this May 16, 2024
connoratrug added a commit that referenced this issue May 16, 2024
connoratrug added a commit that referenced this issue May 22, 2024
#3761)

feat: Some data items under section 'Access conditions' in Cohort view are not shown or need to be renamed

Closes #3600
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.

3 participants