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.

Sign up for GitHub

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

Jump to bottom

Duplicate Transaction #75

Open
M-Zuber opened this issue Apr 5, 2015 · 3 comments
Open

Duplicate Transaction #75

M-Zuber opened this issue Apr 5, 2015 · 3 comments
Labels
Feature Future Release Low Priority

Comments

@M-Zuber
Copy link
Owner

M-Zuber commented Apr 5, 2015

If all fields are exactly the same it is a duplicate.
@M-Zuber
Copy link
Owner Author

M-Zuber commented Apr 5, 2015

If a duplicate is detected the user should be allowed to save it anyway - after confirmation.

@M-Zuber M-Zuber changed the title Duplicate Expense Duplicate Transaction Apr 5, 2015
@M-Zuber M-Zuber self-assigned this Apr 15, 2015
@M-Zuber
Copy link
Owner Author

M-Zuber commented May 14, 2015

see #77 for implementation. The feature spec still needs to be added.

@M-Zuber
Copy link
Owner Author

M-Zuber commented Jul 5, 2015

Moved back to low priority due to PR not being accepted.

@M-Zuber M-Zuber removed their assignment Aug 2, 2015
@M-Zuber M-Zuber removed the Testing label Nov 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Future Release Low Priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@M-Zuber