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

[Feature] Duplicating a reconciled transaction without locking it #2110

Closed
1 of 2 tasks
shall0pass opened this issue Dec 21, 2023 · 3 comments
Closed
1 of 2 tasks

[Feature] Duplicating a reconciled transaction without locking it #2110

shall0pass opened this issue Dec 21, 2023 · 3 comments
Labels
feature This issue is a feature request needs votes Please upvote this feature request if you would like to see it implemented!

Comments

@shall0pass
Copy link
Contributor

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

When using the duplicate feature, I think it would be practical to not duplicate the cleared status if the transaction is reconciled and locked. If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated. It would be a little less inconvenient if we could use the duplicate feature to recreate the transaction without the lock status.

Describe your ideal solution to this problem

No response

Teaching and learning

No response

@shall0pass shall0pass added the feature This issue is a feature request label Dec 21, 2023
@github-actions github-actions bot added the needs votes Please upvote this feature request if you would like to see it implemented! label Dec 21, 2023
Copy link
Contributor

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@MatissJanis
Copy link
Member

If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated.

Alternatively (and I know that this is controversial): we just let people to un-lock transactions. Seems like a much simpler solution to the problem.

@shall0pass
Copy link
Contributor Author

If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated.

Alternatively (and I know that this is controversial): we just let people to un-lock transactions. Seems like a much simpler solution to the problem.

I'm coming around on this. There isn't much of a difference between invalidating the reconciliation by unlocking a transaction vs invalidating it by deleting a transaction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature This issue is a feature request needs votes Please upvote this feature request if you would like to see it implemented!
Projects
None yet
Development

No branches or pull requests

2 participants