Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 8.5.2 MInor Release
-
Labels:
-
Story Points:0.25
-
Sprint:Sprint 30
Description
Currently, a user may lower their Max cache size lower than the current cache size. When this happens, nothing is removed from the cache, and there is no indication that anything has been done.
Instead, there is a message allowing the user to increase their cache size to the necessary size the next time that IGB tries to cache a file.
We should figure out a way to handle this scenario so that the user can have some confirmation that the max cache size is being set below the current cache size.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Story Points | 0.25 |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs Testing [ 10002 ] |
| Assignee | John Eckstein [ jeckstein ] | Mason Meyer [ mason ] |
| Status | Needs Testing [ 10002 ] | Testing In Progress [ 10003 ] |
| Fix Version/s | 8.5.2 MInor Release [ 10200 ] |
| Assignee | Mason Meyer [ mason ] | David Norris [ dcnorris ] |
| Resolution | Done [ 10000 ] | |
| Status | Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | Open [ 1 ] |
| Labels | Cache |
| Resolution | Done [ 10000 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | Loraine Lab Workflow [ 16685 ] | Fall 2019 Workflow Update [ 19715 ] |
| Workflow | Fall 2019 Workflow Update [ 19715 ] | Revised Fall 2019 Workflow Update [ 21834 ] |