mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 15:14:02 -05:00
[GH-ISSUE #2147] Multi-currency support #98252
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#98252
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @oboxodo on GitHub (Dec 31, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2147
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Disclaimer: I know there are requests for multi-currency support in discussions, like https://github.com/actualbudget/actual/discussions/143, but discussions are closed so I figured I'd reopen the subject here.
Is there anyone already working on this? Need help? I don't have much time available and my main language is Ruby, but I'd love to make Actual work for me (and certainly a lot more people) with multi-currency.
I'm happy to collaborate with others sponsoring this development too.
Describe your ideal solution to this problem
I think the proposals from the discussions are just fine.
Eventually, we can also automate getting suggested exchange rates but that's totally optional and should always be overidable.
If you want a role model to mimic, wiz.money seems to do this right.
Teaching and learning
I think this feature can be totally transparent for users who don't need it. Everything uses a single currency by default and the UI doesn't even need to change until an account using a currency different than the budget's is involved. And even then, we can decide if values should be displayed in one currency or the other, or both. What's important is that the values are saved with an exchange rate when needed.
@github-actions[bot] commented on GitHub (Dec 31, 2023):
✨ 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 👍!
@Jackenmen commented on GitHub (Dec 31, 2023):
If you're interested in multiple currencies, this is the most up-to-date (and 7th most upvoted issue in general) issue about it: #1132
Since the interest is evaluated by upvotes, making another issue for this sort of thing is IMO a bit counter-productive. If you have ideas that haven't been expressed yet, it's probably better to suggest them in the above issue since if anyone tries picking this up (and it's a complicated topic requiring quite a bit of designing behind it), they will probably look through that issue the most.
@oboxodo commented on GitHub (Dec 31, 2023):
I swear I had searched for existing issues talking about this but somehow I didn't see that.
Anyway, I upvoted there already.
@youngcw commented on GitHub (Dec 31, 2023):
@oboxodo can this one be closed then if #1132 is sufficient?
@oboxodo commented on GitHub (Dec 31, 2023):
I think it's automatically closed already, isn't it?