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
Describe the Bug
In the genetic worth section of the review form, there are differences in data being shown when in editing mode versus read only mode.
When the user is edit mode and they have recalculated the GW of the seedlot, this is what they see:
When the changes are saved and the user is in read only mode, the tested parent tree percentages are dropped and shown as zero:
Impact and Priority
medium, inconsistent data values will confuse users
Expected Behaviour
the read only mode should accurately show the test parent tree percentages
** Steps To Reproduce**
Steps to reproduce the behaviour:
Go to seedlot '63210' review form
Scroll down to 'Genetic worth and percentage of tested parent tree contribution'
See error
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
the 'T' in tested in the head should also be made a low case
The text was updated successfully, but these errors were encountered:
Describe the Bug
In the genetic worth section of the review form, there are differences in data being shown when in editing mode versus read only mode.
When the user is edit mode and they have recalculated the GW of the seedlot, this is what they see:
When the changes are saved and the user is in read only mode, the tested parent tree percentages are dropped and shown as zero:
Impact and Priority
medium, inconsistent data values will confuse users
Expected Behaviour
the read only mode should accurately show the test parent tree percentages
** Steps To Reproduce**
Steps to reproduce the behaviour:
Go to seedlot '63210' review form
Scroll down to 'Genetic worth and percentage of tested parent tree contribution'
See error
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
the 'T' in tested in the head should also be made a low case
The text was updated successfully, but these errors were encountered: