Actions
Feature (development) #15305
open
Approve transactions start next after finish previous (for example buy LB)
Status:
New
Priority:
High
Assignee:
Target version:
WWW - V4 - all paths lead to QORPO.WORLD
Start date:
08/23/2024
Due date:
% Done:
0%
Estimated time:
custom category:
Backend
Pull Request:
Co-assignee:
Sprint:
QWorld 2026 main (Jun 03 - Nov 30)
Description
Scenario, buy LB by each on UI:
'1. Common
'2. Rare
'3. Epic
- Because of approval it FAILD on BC.
- Solution: User can start several "Jobs", but on BE it has to be processing like "do next after finish previous". On the same chain.
No data to display
Actions