The "BP Usage %" field in the ACCOUNTS overview panel (at the top) does not get updated on trades.
However, clicking on "Cap Req" updates the value.
User Impact
Stocks having earnings are usually high in BPR, which means I overextend a bit my % allocation when I put them on. When closing trades in the morning, I expect to see the BPR% reduce right after exiting. It does not.
Steps to reproduce
Make sure "BP Usage %" is included in the ACCOUNT overview list.
Look at the value of the "BP Usage %"
Place a trade, take note of the BPR difference you should see.
Witness no change in the %.
Click on "Cap Req"
Witness the value change instantly.
There may be other events triggering an update. I'm not sure what they are. Changes in BPR should overall should definitely one of them. It's probably just missing a callback.
Expected Behavior
The "BP Usage %" is updated, at least for large changes in BPR>
Platform Details
TW version: 1.14.4
OS: Linux PopOS! (System76 derivative of Ubuntu 20.10)
Java: Zulu11
lumia:~$ java -version
openjdk version "11.0.11" 2021-04-20 LTS
OpenJDK Runtime Environment Zulu11.48+21-CA (build 11.0.11+9-LTS)
OpenJDK 64-Bit Server VM Zulu11.48+21-CA (build 11.0.11+9-LTS, mixed mode)
Resolution
2021-05-18
Thanks for alerting us to this bug. We've created a ticket for this issue and the development team will be working to get the problem fixed. We appreciate your continued patience and support!
https://docs.google.com/document/d/1wLUDNFVO1TznwBW7S9JtuenFyO__JGAXbLl8Fjxoeok/
Reporter: Martin Blais Date: 5/18/2021
Description of problem
The "BP Usage %" field in the ACCOUNTS overview panel (at the top) does not get updated on trades. However, clicking on "Cap Req" updates the value.
User Impact
Stocks having earnings are usually high in BPR, which means I overextend a bit my % allocation when I put them on. When closing trades in the morning, I expect to see the BPR% reduce right after exiting. It does not.
Steps to reproduce
There may be other events triggering an update. I'm not sure what they are. Changes in BPR should overall should definitely one of them. It's probably just missing a callback.
Expected Behavior
The "BP Usage %" is updated, at least for large changes in BPR>
Platform Details