Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Labels:None
-
Epic Link:
Description
In the Graphs tab there are textboxes that allow a user to enter in whatever value they want for the "Min" and "Max" y-axis values.
When a graph is created there is a default "Min" and "Max" created that can be seen in these textboxes. The "Min" default is 0 but the "Max" default is dependent upon the specific graph track.
If a user attempts to increase the "Max" value (from say 80 to 100) the graph track updates accordingly.
But then, if a user adjust either the left or right edge of the y-axis slider then the "Max" value reverts to its default. This can cause frustration for a user.
Try this activity to illustrate the issue:
*Create a graph track and attempt to lower the height of the graph without decreasing the track height.
You will find that this can't be done without inputting a "Max" value that is greater than the default. Attempting to fine tune this with the slider will cause the "Max" value to revert to its default, so the only way to get it just right is to keep entering a "Max" value over and over until you get it just right.
Attachments
Activity
It may be better to remove the y-axis slider all together and just have the "Min" and "Max" text boxes to avoid the frustration of the "Max" value reverting to the default once the slider is adjusted.
We could also add an "Optimize Graph Height" button here to make this more consistent with the Annotation tab (especially since a user recently asked how to optimize the graph height in HELP-109).
The functionality is already in place because, as stated in this story, the "Max" value gets adjusted to display the "optimal graph height" once the slider is adjusted, so I think all we would need to do is create a button for this action. This would also be particularly useful when you have to scroll to a different area of the genome; you could simply click "Optimize Graph Height" to see the graph at its optimal height.
Assigning to Ann so that she can review the issue and determine whether this should be fixed for the minor release. If so, let me know and I will add it to the 8.3.3 Minor Release epic.