-
Notifications
You must be signed in to change notification settings - Fork 569
[1] Preferred Market Pairing Resets to null When Updating UIA #1420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
[3] Bug
Classification indicating the existing implementation does not match the intention of the design
Milestone
Comments
Closed the wrong issue. |
Increased hours slightly to 1 hr I've updated the Asset Update page with a few tweeks
|
Yeah so what was happening was I could change pairing, but as the pairing
didn't persist as a placeholder; the next time I updated some other aspect
of the UIA, the pairing would reset to BTS.
Cheers.
…On 17 April 2018 at 04:15, startailcoon ***@***.***> wrote:
Closed #1420 <#1420>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1420 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWnLgFwHj__qaBVDgO9LGcbcpt7aNHmwks5tpN_HgaJpZM4TPYiO>
.
|
Cryptolero
pushed a commit
to CryptoBridge/cryptobridge-ui
that referenced
this issue
Nov 2, 2018
…tPair Issue bitshares#1420 - Update Asset Issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
[3] Bug
Classification indicating the existing implementation does not match the intention of the design
Preferred market pairing resets to null when updating UIA. Occurred on wallet.bitshares.org and openledger.io so not sure if UI or core issue.
The text was updated successfully, but these errors were encountered: