Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 8.4.3 Minor Release
-
Labels:
-
Epic Link:
-
Sprint:Sprint 26
Description
Found by Ivory:
By default IGB goes to the first chromosome in the genome. I go the chloroplast chromosome and add a couple bed files to view. load data, all is well. I remove one of my bed files (using x in data table). The track disappears (good) and IGB moves back to the first chromosome (bad).
I found this while working in the tomato genome.
This happens consistently when I use local files (added via drag and drop). I think I got it to happen once with the same files loaded through local quickload, but I tried several times to make it happen again with the quickload and it never did.
Attachments
Activity
I tested this issue on 8.4.3 and 8.5.0 by checking to see if IGB jumped back to Chr1 when deleting a local track from a different chromosome.
I tested the delete action using the red X under the data management table, the option under a track context menu, and the option under the file menu.
I also bookmarked a location on a chromosome other than chromosome 1, restarted IGB, and tried to delete a local track to see if session restart affected anything.
This issue is now functioning as expected on 8.4.3 but still needs to be tested on 8.5.0.
fixed on igb_8_5 and merged to master