Details
Description
The round-robin priority schedule used by the abstract module to choose a module row should consider the account limit setting.
Currently, it only considers the total. By not considering the account limit for a module row, it's possible to exceed it.
Consider 2 module rows added in a group:
- Used 5, limit 5
- Used 5, limit 10
In this case, round-robin would choose the first option, exceeding the limit.
i.e.
- Used 6, limit 5
- Used 5, limit 10
However, it is preferable to select all module rows that have not yet been exceeded before exceeding them. CORE-2138 would then make this soft limit into a hard limit of not exceeding them at all.
Issue Links
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
Story Points | 3 |
Tyson Phillips (Inactive)
made changes -
Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
Sprint | 4.1.0 Sprint 2 [ 39 ] |
Jonathan Reissmueller
made changes -
Assignee | Jonathan Reissmueller [ jonathan ] |
Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
Status | Open [ 1 ] | In Progress [ 3 ] |
Automated transition triggered when Jonathan Reissmueller created pull request #252 in Stash -
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Jonathan Reissmueller
made changes -
Fix Version/s | 4.1.0 [ 11007 ] | |
Fix Version/s | Short Term [ 10800 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #252 in Stash -
Status | In Review [ 5 ] | Closed [ 6 ] |