Enhanced Take-profit and Stop-loss inputs

[kappacappa]

Users have repeatedly voiced the need for easier TP/SL inputs.

Those inputs should at minimum have buttons like the Limit and Stop price inputs (+1%, +2%, etc.) and also show the P/L amount and P/L percent corresponding to the user's input.

Ideally, we should find a UX that lets the user input price, percent, or P/L amount for both TP and SL. Currently, the user can only input price.

---

Bounty

• This issue has a bounty of $200, paid in crypto.
• Bounties are paid upon full resolution of the issue with high quality code, within a reasonable timeframe.
• Important: To be eligible for the bounty, comment below to request assignment to this issue.

[devgreek]

I'll fix this issue.

[kappacappa]

@adebayokehinde ok. Please note the full issue involves creating a new UX, likely in a dropdown inside the input or in a modal, that allows the user to input price, percent, or P/L for both TP and SL.

This would be similar in fashion to the Binance UI.

[devgreek]

Okay no problem

[davidweb3-ctrl]

I would like to work on this bounty. I can enhance the take-profit and stop-loss inputs with better UX, validation, and visual indicators for improved trading experience.

[qq33357486]

Requesting assignment/consideration for this bounty. I opened PR #126 with a focused TP/SL input enhancement and build validation.

[Jiangzhewen]

Opened PR #144 with a fuller TP/SL UX: quick target buttons plus synchronized price, percent, and P/L amount inputs for both take-profit and stop-loss.

[taherdhanera]

Requesting assignment / consideration for this bounty.

Implementation plan:

• Add quick TP/SL presets that mirror the existing limit/stop price shortcuts.
• Let TP and SL be edited by target price, P/L percent, or P/L amount, with the fields kept in sync for both long and short positions.
• Show calculated P/L amount and percent next to the current TP/SL values.
• Keep the change scoped to the order-entry controls and avoid unrelated trading logic.
• Add focused validation or component-level coverage if the repo test setup supports it.