Skip to content
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

New Asset Transaction from Dashboard #2672

Closed
Leosirth opened this issue Oct 1, 2019 · 2 comments
Closed

New Asset Transaction from Dashboard #2672

Leosirth opened this issue Oct 1, 2019 · 2 comments
Labels
enhancement Requests for enhancements of existing stuff. fixed Bugs that are fixed (in a coming release).

Comments

@Leosirth
Copy link

Leosirth commented Oct 1, 2019

Bug description
In the dashboard page there is the asset list to the right with a "Create new transaction" button for each asset.

Clicking on one of this shouldn't it auto-fill i.e. the source account based on the asset for which the button has been clicked?
Otherwise it's a useless repetition to have the "Create new transaction" repeated for every asset.

Maybe the button can be splitted in "Create new Withdrawal" and "Create new Deposit" and auto-fill the Source or Destination account accordingly.

What is your thoughts?
Thanks and regards,

@JC5
Copy link
Member

JC5 commented Oct 1, 2019

Both used to be the case. I'll mark it as an enhancement.

@JC5 JC5 added the enhancement Requests for enhancements of existing stuff. label Oct 1, 2019
@JC5
Copy link
Member

JC5 commented Mar 13, 2020

This will work again in the next release.

@JC5 JC5 added the fixed Bugs that are fixed (in a coming release). label Mar 13, 2020
@JC5 JC5 closed this as completed in 8724ba0 Mar 13, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests for enhancements of existing stuff. fixed Bugs that are fixed (in a coming release).
Projects
None yet
Development

No branches or pull requests

2 participants