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
If this is a bug, please explain how to reproduce the problem
Which tools did you use in which sequence?
Is the error concerning a text or a volume annotation?
Which label set has been used for the volume annotation (if applicable)?
What is the type and resolution of your data? (Can you provide a link to your data?)
Do not include sensitive information.
Upload the browser error message if you are familiar with web developer tools.
In the project setting page we have the possibility to change a volume annotation type. But when we do this and go back to project page, the MRI still has the old annotation type, because the annotation type for the project is written in the mri entry at the creation of the annotation and not modified after.
Expected behaviour
The MRI annotation should follow the project annotation. It would seem more natural that the project annotation is not stored in the mri entry but in the project entry as it is only specific to the project, and the same mri can be used by multiple projects. At least it should not be possible to update the annotation type for the project if it is not possible to do it for the mri of the project.
Version information (for bug reports)
Browser + version:
Your OS + version:
Paste the output of these commands:
node --version && npm --version
newest (master and pr branches)
The text was updated successfully, but these errors were encountered:
Thank you for your feedback.
Is it a [x] bug report or a [ ] feature request?
Current behaviour
In the project setting page we have the possibility to change a volume annotation type. But when we do this and go back to project page, the MRI still has the old annotation type, because the annotation type for the project is written in the mri entry at the creation of the annotation and not modified after.
Expected behaviour
The MRI annotation should follow the project annotation. It would seem more natural that the project annotation is not stored in the mri entry but in the project entry as it is only specific to the project, and the same mri can be used by multiple projects. At least it should not be possible to update the annotation type for the project if it is not possible to do it for the mri of the project.
Version information (for bug reports)
newest (master and pr branches)
The text was updated successfully, but these errors were encountered: