-
Notifications
You must be signed in to change notification settings - Fork 570
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
[1][gibbsfromncis] Add operation ID to transaction history #450
Comments
It's part of the UX for the new tables. #378 |
#378 has been closed. The ID is still not there. |
@wmbutler can I take this one? Where exactly the ID should be? |
@gibbsfromncis please send questions to OP |
@Ashaman- can you provide more information? If not we will close this issue. |
It means adding an "operation_id" column or something similar in account history. Needs UX. |
To be clear, operation ID is "1.11.XXX". |
This is a fairly easy add to activity. I don't think it requires UX. |
Easy win. @gibbsfromncis please either work it or give it up. |
PR: #1310 |
#450 Add transaction id to account activity
bitshares#450 Add transaction id to account activity
OpenLedger have added an "operation id" to the transaction history in their wallet. They require the ID be provided with a support request when opening a ticket relating to problems with a withdrawal. https://openledger.freshdesk.com/support/solutions/articles/33000206336-how-to-identify-withdrawal-transaction-
It would be very convenient if the desktop wallet included this (maybe hidden by default with a button to show it), because otherwise we have to jump through hoops backing up our wallets and importing the backup into OL's wallet if we need to open a ticket in response to an error with their gateway service.
The text was updated successfully, but these errors were encountered: