Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Trivial
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0
-
Epic Link:
-
Sprint:Sprint 24
Description
It seems that there is a bug with the residue search.
If a user performs a residue search for a region where they have manually loaded the sequence (using the "Load Sequence" button) then the user will only get results from the positive strand (this behavior is wrong).
If a user performs a residue search for a region where the sequence has not been manually loaded then the user will get results from the positive and negative strands (this behavior should always happen).
We should fix this so that the residue search searches both positive and negative strands as this is definitely most useful to users.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-439 [ 15497 ] |
| Rank | Ranked higher |
| Sprint | Backlog Grooming Meeting [ 29 ] |
| Rank | Ranked lower |
| Assignee | David Norris [ dcnorris ] | Mason Meyer [ mason ] |
| Story Points | 0 |
| Rank | Ranked lower |
| Summary | Residue search does not search both strands if user manually loads sequence | Residue search does not search both strands sometimes, not able to reproduce yet |
| Summary | Residue search does not search both strands sometimes, not able to reproduce yet | Residue search does not search both strands sometimes, not able to reproduce |
| Summary | Residue search does not search both strands sometimes, not able to reproduce | Residue search does not appear to always search both strands, but can't reproduce reliably |
| Sprint | Backlog Grooming Meeting [ 29 ] | Sprint 20 [ 25 ] |
| Rank | Ranked higher |
| Status | Open [ 1 ] | Testing In Progress [ 10003 ] |
| Status | Testing In Progress [ 10003 ] | Needs Testing [ 10002 ] |
| Sprint | Sprint 20 [ 25 ] |
| Sprint | Sprint 21 [ 26 ] |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Status | Needs Testing [ 10002 ] | Testing In Progress [ 10003 ] |
| Status | Testing In Progress [ 10003 ] | Needs Testing [ 10002 ] |
| Rank | Ranked higher |
| Priority | Major [ 3 ] | Trivial [ 5 ] |
| Sprint | Sprint 21 [ 26 ] |
| Sprint | Backlog Grooming Meeting [ 29 ] |
| Rank | Ranked higher |
| Sprint | Backlog Grooming Meeting [ 29 ] |
| Rank | Ranked lower |
| Sprint | Backlog Grooming Meeting [ 32 ] |
| Rank | Ranked lower |
| Sprint | Backlog Grooming Meeting [ 32 ] | Sprint 24 [ 31 ] |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Status | Needs Testing [ 10002 ] | Testing In Progress [ 10003 ] |
Further testing revealed no evidence that the issue in this story is still present in IGB. Since there seems to be no issue present I am now closing this issue.
| Resolution | Done [ 10000 ] | |
| Status | Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Status | Closed [ 6 ] | Closed [ 6 ] |
| Workflow | Loraine Lab Workflow [ 15927 ] | Fall 2019 Workflow Update [ 19489 ] |
| Workflow | Fall 2019 Workflow Update [ 19489 ] | Revised Fall 2019 Workflow Update [ 21606 ] |
Upon further examination it seems that this behavior is not reproducible using the information listed above. We should look into this further to determine why the residue search searches the positive strand only sometimes but sometimes searches both strands.