mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 14:43:36 -05:00
Request to duplicate transactions #47
Closed
opened 2026-02-28 18:46:35 -06:00 by GiteaMirror
·
8 comments
No Branch/Tag Specified
master
tabedzki/feat/replacing-month-picker-with-day-picker
enforce-append-only-migrations-ci
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
cross-version-sync-compat
claude/error-codes-worker-boundary-26i5uu
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
api-browser-custom-data-dir
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/react-table-library-research-afx83z
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
release
ai-fix-cleanup-def-8290
claude/relaxed-shannon-jusywa
claude/fervent-keller-s6f2fq
claude/determined-feynman-st1y9z
claude/wizardly-einstein-vi2wce
claude/sweet-albattani-7nseio
feat/bank-sync-per-budget-file
claude/affectionate-cannon-y0kc82
claude/dependabot-findings-m9pgmb
claude/mac-app-ios-publish-zjs1lz
claude/vigilant-tesla-aiiyos
depot-migrate-secrets-1781296330308
claude/quirky-cerf-v5qck7
claude/animation-removal-alternative-2etfh1
claude/netlify-preview-comments-consolidate-9XPYa
osc/7391-error-boundaries-reports
claude/pensive-dijkstra-7DYui
claude/server-app-version-mismatch-HTCGv
claude/pr-8027-review-feedback-mELuO
claude/zealous-wozniak-e5pO0
claude/intelligent-heisenberg-BSHJq
claude/translation-download-refactor-jFRsO
claude/mobile-performance-ideas-G9PAO
claude/github-issue-7988-5A5ly
blacksmith-migration-ff70d2d
claude/great-mayer-KRvOk
claude/react-native-ios-compilation-fcJh5
claude/serene-goldberg-58xv0
claude/kind-euler-LVG3K
release-automation/edge-nightly
7710-bundle-migrations
claude/fix-docker-build-error-WMfed
claude/llm-compatible-release-notes-t20Nr
7710-tests-tdd
cursor/transaction-table-rewrite-f077
claude/plan-ci-secure-context-OtEe1
claude/fix-issue-7667-DPXi3
cursor/resolve-pr-7449-ee11
claude/fix-typescript-build-error-JPtZ5
copilot/add-repository-configs-to-packages
worktree-compressed-drifting-ritchie
claude/api-consumer-verification-kfz1K
pr-7454
claude/fix-issue-7410-LLLQ4
revert-7281-generate-icons
react-query-useSchedules
copilot/sub-pr-6140
package-upgrades
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#47
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking 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 @triplejranch on GitHub (Feb 28, 2022).
I searched and didn't find this, but forgive me if I missed it. It would be really handy if we could select a transaction and duplicate it so we could just change the date and be on our way. I'm thinking of transactions I have that have multiple splits and I repeat monthly. A big time saver.
@Deguello commented on GitHub (Feb 28, 2022):
For non-splits, you can set up schedules. For splits, I think that ability is being added to schedule functionality.
I agree it would be nice to copy and paste a transaction. Copy and paste with a transaction selected seems to do nothing. If it's not going to do anything, there should be an indiction of that in the menu. Right now, Copy looks greyed out, but it copies individual fields in a transaction but appears to copy nothing if a transaction is selected.
@triplejranch commented on GitHub (Mar 1, 2022):
Yes, if schedules could do splits, then I'd be set. Copy and paste hasn't worked, I agree. Just thought being able to duplicate might be an option. Thanks:)
@Deguello commented on GitHub (Mar 1, 2022):
Honestly, for now, I just broke my splits into separate transactions. First, it made scheduling easier. Second, the way drill downs from the budget screen work right now, amounts in splits don't show up right and this avoids the issue. Third, they all happen at once, anyway, so clearing them all at once works OK.
I agree with your suggestion and I'm not saying this is how it SHOULD work, but doing it this way is better than nothing for me.
@Kidglove57 commented on GitHub (Mar 1, 2022):
“I just broke my splits into separate transactions”
Same here and so far all has been fine. It seemed a big deal initially but not so much when I adapted to it. I add a note to indicate that the scheduled transaction is recorded in two parts, something like:
1 of 2 total £60
and then
2 of 2 total £60.
But yes I agree it’s not ideal
@triplejranch commented on GitHub (Mar 1, 2022):
Ok. To clarify, you're adding separate transactions, not separate schedules? Well, I guess it doesn't matter. Gah, that seems like so much extra work, but then again, I guess it's pretty much the same. Sorry, talking out loud, lol. If I made separate schedule for all my splits, then I would only be doing it once. Got it. Thanks for the workaround tip all! Hey, do you happen to know where this is on his roadmap before I dive into this?
@Kidglove57 commented on GitHub (Mar 1, 2022):
I do have a couple of schedules split into separate transactions. No it's not ideal - but it does the job in the short term whilst this feature is being worked on.
@triplejranch commented on GitHub (Mar 1, 2022):
Hey, I can't get Tools: Find Schedules to do anything. Just nothing. Is there a trick I'm doing wrong or do I not have enough data to trigger anything? I have 3 months worth of transactions, but maybe that's not enough? I thought it would make it easier fo rme, but I can't get it to work.
This is actually probably not where I'm supposed to ask this question. Oops. So many apps.
@jlongster commented on GitHub (Mar 1, 2022):
@triplejranch hey! it's hard to say -- it will look for something occurring 3 times I believe. So you may not have just enough data yet. They also have the match payees.
Duplicating is an interesting idea, but I'd rather invest time in getting splits to work in rules (and thus schedules) :) I think I'm gonna work on this very soon, not the next release but the one after that. I'm working on https://github.com/actualbudget/releases/issues/218 so it would be natural to allow splits in rules after this, then you can have scheduled transfers in splits as well.