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
The tagging screen in Limber seems to have stop showing a preview of the wells, with the tag index inside the well. Reported in RT 798827 (and 799378).
RT Ticket Number
798827
To Reproduce
Steps to reproduce the behaviour:
Run 'Bespoke PCR' spec in Integration Suite, stopping the test when you get to the tagging screen
See that wells are blank
Expected behaviour
Coloured boxes appear indicating wells, with numbers inside indicating tags. See screenshots.
Screenshots
Screenshot from a while ago showing tagging screen with yellow wells:
Screenshot from the RT showing blank wells:
Desktop (please complete the following information):
My test was on a Mac, using Google Chrome (Version 122.0.6261.128 (Official Build) (x86_64))
The text was updated successfully, but these errors were encountered:
KatyTaylor
changed the title
Y24-nnn [BUG] Limber tagging screen not showing wells with tag index
Y24-029 [BUG] Limber tagging screen not showing wells with tag index
Mar 15, 2024
Was discussed and mentioned at stand up (19/3) that there were JS changes a few weeks ago. The contacts in the RT mention that this has been a noted issue for the "..past few weeks"
Describe the bug
The tagging screen in Limber seems to have stop showing a preview of the wells, with the tag index inside the well. Reported in RT 798827 (and 799378).
RT Ticket Number
798827
To Reproduce
Steps to reproduce the behaviour:
Run 'Bespoke PCR' spec in Integration Suite, stopping the test when you get to the tagging screen
See that wells are blank
Expected behaviour
Coloured boxes appear indicating wells, with numbers inside indicating tags. See screenshots.
Screenshots
Screenshot from a while ago showing tagging screen with yellow wells:
Screenshot from the RT showing blank wells:
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: