[GH-ISSUE #531] [Feature] Ability to add tags to transactions #7143

New Issue

GiteaMirror · 2026-04-10T16:50:21-05:00

GiteaMirror commented

2026-04-10 16:50:21 -05:00

Originally created by @rich-howell on GitHub (Jan 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/531

Discussed in https://github.com/actualbudget/actual/discussions/151

^{Originally posted by winklevos August 6, 2022}
Add a field to capture tags onto a transaction for later filter,

i.e tag a transactions with tax one-off

Originally created by @rich-howell on GitHub (Jan 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/531 ### Discussed in https://github.com/actualbudget/actual/discussions/151 <div type='discussions-op-text'> <sup>Originally posted by **winklevos** August 6, 2022</sup> Add a field to capture tags onto a transaction for later filter, i.e tag a transactions with `tax` `one-off`</div>

GiteaMirror added the feature label 2026-04-10 16:50:21 -05:00

GiteaMirror closed this issue

2026-04-10 16:50:21 -05:00

GiteaMirror commented

2026-04-10 16:50:22 -05:00

@MatissJanis commented on GitHub (Jan 23, 2023):

@winklevos

Although we currently don't fully support search by tags, you can still use the notes field for them.

For example: #tax #one-off in the notes field

Given this: closing

@MatissJanis commented on GitHub (Jan 23, 2023): @winklevos Although we currently don't fully support search by tags, you can still use the notes field for them. For example: `#tax #one-off` in the notes field Given this: closing

GiteaMirror commented

2026-04-10 16:50:22 -05:00

@albertogasparin commented on GitHub (Mar 8, 2023):

Hello, not sure what was discussed in #151 as it shows locked with 0 comments, but I'd like to add another reason why tags can become very useful: reporting and overview.

For instance, I do have a holiday category. I currently use notes as a way to group expenses by holiday destination but it is hard to visualise the impact of each on my yearly monthly budget. I have to manually select transactions in order to see their totals, and if in the future we will have better reports (for instance by category) it would be great to group by tags.

Hope it makes sense.

@albertogasparin commented on GitHub (Mar 8, 2023): Hello, not sure what was discussed in #151 as it shows locked with 0 comments, but I'd like to add another reason why tags can become very useful: reporting and overview. For instance, I do have a holiday category. I currently use notes as a way to group expenses by holiday destination but it is hard to visualise the impact of each on my yearly monthly budget. I have to manually select transactions in order to see their totals, and if in the future we will have better reports (for instance by category) it would be great to group by tags. Hope it makes sense.

GiteaMirror commented

2026-04-10 16:50:23 -05:00

@Kidglove57 commented on GitHub (Mar 8, 2023):

100% agree with this suggestion

@Kidglove57 commented on GitHub (Mar 8, 2023): 100% agree with this suggestion

GiteaMirror commented

2026-04-10 16:50:24 -05:00

@GurjinderSingh commented on GitHub (Mar 13, 2023):

currently I am using Firefly and it have tags based on rules. multiple tag can be used
https://demo.firefly-iii.org/transactions/edit/450

only problem with Firefly is refund transactions are not allowed and developer said its accountant suggestion

@GurjinderSingh commented on GitHub (Mar 13, 2023): currently I am using Firefly and it have tags based on rules. multiple tag can be used https://demo.firefly-iii.org/transactions/edit/450 only problem with Firefly is refund transactions are not allowed and developer said its accountant suggestion

GiteaMirror commented

2026-04-10 16:50:24 -05:00

@github-actions[bot] commented on GitHub (May 1, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!

@github-actions[bot] commented on GitHub (May 1, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!

GiteaMirror commented

2026-04-10 16:50:25 -05:00

@YagiOoda commented on GitHub (May 7, 2023):

I would really like this feature however it is implemented. I think even using the notes field and autocompleting based in "#" would be really helpful!

@YagiOoda commented on GitHub (May 7, 2023): I would really like this feature however it is implemented. I think even using the notes field and autocompleting based in "#" would be really helpful!

GiteaMirror commented

2026-04-10 16:50:26 -05:00

@jimmys888 commented on GitHub (Aug 28, 2023):

I would really like this feature however it is implemented. I think even using the notes field and autocompleting based in "#" would be really helpful!

Second this. Most of the time I forget what tags I've entered in the past, so using autocomplete when typing # in the notes field is beneficial. Maybe a dedicated page to manage the tags? If a tag that's not in the tags list is entered, the user should add it to the list to appear in the autocomplete.

@jimmys888 commented on GitHub (Aug 28, 2023): > I would really like this feature however it is implemented. I think even using the notes field and autocompleting based in "#" would be really helpful! Second this. Most of the time I forget what tags I've entered in the past, so using autocomplete when typing `#` in the notes field is beneficial. Maybe a dedicated page to manage the tags? If a tag that's not in the tags list is entered, the user should add it to the list to appear in the autocomplete.

GiteaMirror commented

2026-04-10 16:50:27 -05:00

@Kidglove57 commented on GitHub (Aug 28, 2023):

I would also ideally like this tag feature to be implemented. I have a decent workaround at the moment. I enter a note in tag style in the notes field. I have quite a number of saved filters which reference specific "tags" and thus enable me to gather all the data I need.

@Kidglove57 commented on GitHub (Aug 28, 2023): I would also ideally like this tag feature to be implemented. I have a decent workaround at the moment. I enter a note in tag style in the notes field. I have quite a number of saved filters which reference specific "tags" and thus enable me to gather all the data I need.

GiteaMirror commented

2026-04-10 16:50:27 -05:00

@jimmys888 commented on GitHub (Aug 28, 2023):

I would also ideally like this tag feature to be implemented. I have a decent workaround at the moment. I enter a note in tag style in the notes field. I have quite a number of saved filters which reference specific "tags" and thus enable me to gather all the data I need.

That is a good idea. It's just that I often forget what tag(s) I entered for a transaction, and when I'm doing the same transaction I have to look for the older ones to see what tags I assigned. Autocomplete feature will help a lot.

@jimmys888 commented on GitHub (Aug 28, 2023): > I would also ideally like this tag feature to be implemented. I have a decent workaround at the moment. I enter a note in tag style in the notes field. I have quite a number of saved filters which reference specific "tags" and thus enable me to gather all the data I need. That is a good idea. It's just that I often forget what tag(s) I entered for a transaction, and when I'm doing the same transaction I have to look for the older ones to see what tags I assigned. Autocomplete feature will help a lot.

GiteaMirror commented

2026-04-10 16:50:28 -05:00

@apilbeam101 commented on GitHub (Nov 21, 2023):

Very much like this idea too.
Particular use-case in mind for me would be thigs like holidays and work expenses.
I would like my actual categories to reflect the purchase type, i.e Flights, Hotels, Food, Activities etc. but then the ability to tag specific spend as "Holiday" or "Work Expenses" means that I can see the breakdown of my costs when travelling as well as be able to ignore my work expenses since they'd be claimed back.

@apilbeam101 commented on GitHub (Nov 21, 2023): Very much like this idea too. Particular use-case in mind for me would be thigs like holidays and work expenses. I would like my actual categories to reflect the purchase type, i.e Flights, Hotels, Food, Activities etc. but then the ability to tag specific spend as "Holiday" or "Work Expenses" means that I can see the breakdown of my costs when travelling as well as be able to ignore my work expenses since they'd be claimed back.

GiteaMirror commented

2026-04-10 16:50:29 -05:00

@Rick-Thomas commented on GitHub (Nov 21, 2023):

I'm all for TAGs... Without this you have to OR duplicate the categories to identify the elements your tracking OR filter using the Notes field, hoping you have a uniform method to identify the elements your tracking...

@Rick-Thomas commented on GitHub (Nov 21, 2023): I'm all for TAGs... Without this you have to _OR_ **duplicate** the categories to identify the elements your tracking _OR_ **filter** using the Notes field, hoping you have a uniform method to identify the elements your tracking...

GiteaMirror commented

2026-04-10 16:50:31 -05:00

@thoughtlessmind commented on GitHub (Dec 10, 2023):

this would be a good addition to manage the subcategory or specific parts of the transactions. Suppose, I want to tag the expenses by the medium they spent, like credit card, direct transfer, UPI, etc. Right now, it's only notes (as suggested above), but that is not optimized as it can't be used in analytics or anywhere efficiently.

@thoughtlessmind commented on GitHub (Dec 10, 2023): this would be a good addition to manage the subcategory or specific parts of the transactions. Suppose, I want to tag the expenses by the medium they spent, like credit card, direct transfer, UPI, etc. Right now, it's only notes (as suggested above), but that is not optimized as it can't be used in analytics or anywhere efficiently.

GiteaMirror commented

2026-04-10 16:50:32 -05:00

@MikesGlitch commented on GitHub (Dec 10, 2023):

Other people have mentioned this, but I'm gonna throw my hat in as well - and provide some screenshots for clarity.

I've started using the notes field for tags like "#interest" and I've found it works great with reporting/analytics. It works well if you save a filter for it, e.g. "Bank account interest" which contains "#interest" and apply it to the report.

I think the downside to adding a new field for tags is we'd be making a new field for something that already "sort of" exists with notes. Maybe Notes should be enhanced, rather than a new thing developed.

Maybe this is a styling issue, could style it like this:

We already have different displays for when we're editing the field vs viewing - so I'd think the "View" would just change to recognise "#{thetag}" and when it see's the hashtag it styles it.

When we're entering the field, we could use the autocomplete control and trigger it when the input see's a "#". If there was a set of tags that you have already used, maybe we could save them somewhere for re-use and populate the autocomplete with them.

That would trigger the normal autocomplete but with a list of tags (excuse my paint skills):

@MikesGlitch commented on GitHub (Dec 10, 2023): Other people have mentioned this, but I'm gonna throw my hat in as well - and provide some screenshots for clarity. I've started using the notes field for tags like "#interest" and I've found it works great with reporting/analytics. It works well if you save a filter for it, e.g. "Bank account interest" which contains "#interest" and apply it to the report. I think the downside to adding a new field for tags is we'd be making a new field for something that already "sort of" exists with notes. Maybe Notes should be enhanced, rather than a new thing developed. Maybe this is a styling issue, could style it like this: ![image](https://github.com/actualbudget/actual/assets/5285928/ed797595-b423-4c29-a4be-a8d2a2ae7704) We already have different displays for when we're editing the field vs viewing - so I'd think the "View" would just change to recognise "#{thetag}" and when it see's the hashtag it styles it. When we're entering the field, we could use the autocomplete control and trigger it when the input see's a "#". If there was a set of tags that you have already used, maybe we could save them somewhere for re-use and populate the autocomplete with them. That would trigger the normal autocomplete but with a list of tags (excuse my paint skills): ![image](https://github.com/actualbudget/actual/assets/5285928/7d3437fb-be04-48d7-9663-986059ec6180)

GiteaMirror commented

2026-04-10 16:50:32 -05:00

@Kidglove57 commented on GitHub (Dec 10, 2023):

@MikesGlitch I do exactly the same as you in the Notes field for any group of transactions I want to report on. A special home project, data for tax etc. Eg #GiftAid, #Interest or #Summerhouse. I would welcome something more formalised style wise!

@Kidglove57 commented on GitHub (Dec 10, 2023): @MikesGlitch I do exactly the same as you in the Notes field for any group of transactions I want to report on. A special home project, data for tax etc. Eg #GiftAid, #Interest or #Summerhouse. I would welcome something more formalised style wise!

GiteaMirror commented

2026-04-10 16:50:33 -05:00

@thoughtlessmind commented on GitHub (Dec 14, 2023):

yes @MikesGlitch
that makes much more sense. there's already a relevant field so creating and managing a new similar field would be useless.

in notes, we can improve how a particular tag is treated, like a suggestion, formatting, bulk edit text of a particular tag, and all..

@thoughtlessmind commented on GitHub (Dec 14, 2023): yes @MikesGlitch that makes much more sense. there's already a relevant field so creating and managing a new similar field would be useless. in notes, we can improve how a particular tag is treated, like a suggestion, formatting, bulk edit text of a particular tag, and all..

GiteaMirror commented

2026-04-10 16:50:33 -05:00

@shawalli commented on GitHub (Feb 4, 2024):

I would love this feature, but I would recommend it be its own field. I think about it like I do for tagging other things. Take the most common programming example, a blog. One of the first things you add to a blog post are tags. They usually have their own input, have auto-complete for existing tags, and support multiple tags. The order doesn't matter, and you can filter by multiple tags.

@shawalli commented on GitHub (Feb 4, 2024): I would love this feature, but I would recommend it be its own field. I think about it like I do for tagging other things. Take the most common programming example, a blog. One of the first things you add to a blog post are tags. They usually have their own input, have auto-complete for existing tags, and support multiple tags. The order doesn't matter, and you can filter by multiple tags.

GiteaMirror commented

2026-04-10 16:50:34 -05:00

@carkom commented on GitHub (Mar 1, 2024):

I'm not convinced that we'd need a new field just for tags. There's no reason you can't have multiple tags in the notes field and there's already functionality to filter by one or multiple tags that are currently in the notes (example screenshot below). The only thing we are missing to make this an integrated feature is auto-complete (which I think everyone agrees on) and formatting (like @MikesGlitch displayed). You could even create a new filterBy type for "tags" that just searches the notes field and uses the aformentioned auto-complete.

@carkom commented on GitHub (Mar 1, 2024): I'm not convinced that we'd need a new field just for tags. There's no reason you can't have multiple tags in the notes field and there's already functionality to filter by one or multiple tags that are currently in the notes (example screenshot below). The only thing we are missing to make this an integrated feature is auto-complete (which I think everyone agrees on) and formatting (like @MikesGlitch displayed). You could even create a new filterBy type for "tags" that just searches the notes field and uses the aformentioned auto-complete. ![image](https://github.com/actualbudget/actual/assets/55785687/13d313d1-0c6c-4633-83ac-9aaede5bb2ce)

GiteaMirror commented

2026-04-10 16:50:34 -05:00

@Teprifer commented on GitHub (Mar 1, 2024):

I'm not convinced that we'd need a new field just for tags. There's no reason you can't have multiple tags in the notes field and there's already functionality to filter by one or multiple tags that are currently in the notes (example screenshot below). The only thing we are missing to make this an integrated feature is auto-complete (which I think everyone agrees on) and formatting (like @MikesGlitch displayed). You could even create a new filterBy type for "tags" that just searches the notes field and uses the aformentioned auto-complete.

I like this approach, a separate column would change available estate, and I suspect adding tags would reduce the need for lengthy notes - sort of an add 1 here, sub 1 there type thing so the sum space needed is about the same.

@Teprifer commented on GitHub (Mar 1, 2024): > I'm not convinced that we'd need a new field just for tags. There's no reason you can't have multiple tags in the notes field and there's already functionality to filter by one or multiple tags that are currently in the notes (example screenshot below). The only thing we are missing to make this an integrated feature is auto-complete (which I think everyone agrees on) and formatting (like @MikesGlitch displayed). You could even create a new filterBy type for "tags" that just searches the notes field and uses the aformentioned auto-complete. > I like this approach, a separate column would change available estate, and I suspect adding tags would reduce the need for lengthy notes - sort of an add 1 here, sub 1 there type thing so the sum space needed is about the same.

GiteaMirror commented

2026-04-10 16:50:34 -05:00

@shawalli commented on GitHub (Mar 2, 2024):

I can get behind that…with searching though, I’d like for the tags to be able to be unordered. For example, “#taxes #hsa” and “#hsa #taxes” should return the same results.

EDIT: can’t -> can

@shawalli commented on GitHub (Mar 2, 2024): I can get behind that…with searching though, I’d like for the tags to be able to be unordered. For example, “#taxes #hsa” and “#hsa #taxes” should return the same results. EDIT: can’t -> can

GiteaMirror commented

2026-04-10 16:50:35 -05:00

@Teprifer commented on GitHub (Mar 2, 2024):

I can get behind that…with searching though, I’d like for the tags to be able to be unordered. For example, “#taxes #hsa” and “#hsa #taxes” should return the same results.

EDIT: can’t -> can

I'd assume tags would default to the contains option for each select, a slightly nicer way of using:

@Teprifer commented on GitHub (Mar 2, 2024): > I can get behind that…with searching though, I’d like for the tags to be able to be unordered. For example, “#taxes #hsa” and “#hsa #taxes” should return the same results. > > EDIT: can’t -> can I'd assume tags would default to the contains option for each select, a slightly nicer way of using: ![image](https://github.com/actualbudget/actual/assets/34882928/9622a214-914c-41bb-ad3c-6a166d1ad4b6)

GiteaMirror commented

2026-04-10 16:50:36 -05:00

@CodingEmil commented on GitHub (Jun 3, 2024):

Is there any news to this?

@CodingEmil commented on GitHub (Jun 3, 2024): Is there any news to this?

GiteaMirror commented

2026-04-10 16:50:36 -05:00

@lelemm commented on GitHub (Jun 10, 2024):

I was trying to tackle this feature based on some messages here, adding tags in notes looks easy but the input component must be rebuild from scratch using a div (with ContentEditable) instead of a input. This open for so many possible problems since it does not have .value attribute.

Any way, the way I made a POC. The video below shows it:

https://github.com/actualbudget/actual/assets/15043428/a110b200-91c8-41f0-a0ef-0e4779d31483

This is far for ready, there are too many events missing (since I changed from input to div). It's just to showcase a possible way to implement this if it makes sense.

WDYT @MatissJanis ?

@lelemm commented on GitHub (Jun 10, 2024): I was trying to tackle this feature based on some messages here, adding tags in notes looks easy but the input component must be rebuild from scratch using a div (with ContentEditable) instead of a input. This open for so many possible problems since it does not have .value attribute. Any way, the way I made a POC. The video below shows it: https://github.com/actualbudget/actual/assets/15043428/a110b200-91c8-41f0-a0ef-0e4779d31483 This is far for ready, there are too many events missing (since I changed from input to div). It's just to showcase a possible way to implement this if it makes sense. WDYT @MatissJanis ?

GiteaMirror commented

2026-04-10 16:50:37 -05:00

@MatissJanis commented on GitHub (Jun 10, 2024):

@lelemm I'm currently vacationing, so can't do a deep dive this week. But take a look at #2670

@MatissJanis commented on GitHub (Jun 10, 2024): @lelemm I'm currently vacationing, so can't do a deep dive this week. But take a look at #2670

GiteaMirror commented

2026-04-10 16:50:37 -05:00

@lelemm commented on GitHub (Jun 10, 2024):

I just noticed that @MatissJanis / @youngcw . Looks like they took different approach on this

@lelemm commented on GitHub (Jun 10, 2024): I just noticed that @MatissJanis / @youngcw . Looks like they took different approach on this

GiteaMirror commented

2026-04-10 16:50:38 -05:00

@lelemm commented on GitHub (Jun 10, 2024):

Played around with their version. Looks very nice. There are two main differences as I can see:

I tried to use an WYSIWYG approach, they set the tags after done editing the input.
I added a different filter type (has tags) so you can easily search for notes with multiple tags on it without thinking about the order and without using regex

@lelemm commented on GitHub (Jun 10, 2024): Played around with their version. Looks very nice. There are two main differences as I can see: - I tried to use an WYSIWYG approach, they set the tags after done editing the input. - I added a different filter type (has tags) so you can easily search for notes with multiple tags on it without thinking about the order and without using regex

GiteaMirror commented

2026-04-10 16:50:38 -05:00

@psybers commented on GitHub (Jun 12, 2024):

@lelemm Is there a branch/PR somewhere? I think there are things that are nice about both approaches. We might want to consider a merger.

@psybers commented on GitHub (Jun 12, 2024): @lelemm Is there a branch/PR somewhere? I think there are things that are nice about both approaches. We might want to consider a merger.

GiteaMirror commented

2026-04-10 16:50:38 -05:00

@lelemm commented on GitHub (Jun 12, 2024):

@psybers here, created a draft PR for it: https://github.com/actualbudget/actual/pull/2869
It's far from usable, for example, I didn't made the tags clickable like @joel-jeremy version and it's missing many events to mimic the original input field

Lint doesn't like what I did cuz of this lines: raw html

I'm not keep digging this since there is a solution in place for this feature

@lelemm commented on GitHub (Jun 12, 2024): @psybers here, created a draft PR for it: https://github.com/actualbudget/actual/pull/2869 It's far from usable, for example, I didn't made the tags clickable like @joel-jeremy version and it's missing many events to mimic the original input field Lint doesn't like what I did cuz of this lines: [raw html](https://github.com/actualbudget/actual/pull/2869/files#diff-1ec67e99a0958784935973fd65f348c2c881f4b83a0229070edad3cf7349afd7R66) I'm not keep digging this since there is a solution in place for this feature

GiteaMirror commented

2026-04-10 16:50:39 -05:00

@youngcw commented on GitHub (Jun 21, 2024):

Initial support added by #2670. Will be in the next release.

@youngcw commented on GitHub (Jun 21, 2024): Initial support added by #2670. Will be in the next release.

GiteaMirror referenced this issue

2026-04-10 22:10:23 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #14017

GiteaMirror referenced this issue

2026-04-14 22:01:31 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #21325

GiteaMirror referenced this issue

2026-04-16 18:42:28 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #25572

GiteaMirror referenced this issue

2026-04-18 08:51:26 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #32887

GiteaMirror referenced this issue

2026-04-20 23:56:52 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #37157

GiteaMirror referenced this issue

2026-04-23 14:11:21 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #41393

GiteaMirror referenced this issue

2026-04-26 10:40:39 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #48782

GiteaMirror referenced this issue

2026-05-01 03:57:34 -05:00

[PR #7143] [MERGED] Bump dompurify from 3.3.0 to 3.3.2 #56266

Sign in to join this conversation.

Branches Tags

master

claude/hide-default-categories-1cwBZ

matiss/crdt-source-loading

youngcw/unlock-duplicates

matiss/crdt-protobuf

release/26.5.0

claude/update-issue-template-ykMNn

claude/fix-issue-7667-DPXi3

cursor/formula-feedback-improvements-4223

cursor/resolve-pr-7449-ee11

claude/fix-typescript-build-error-JPtZ5

jfdoming/api-tokens-part-3

jfdoming/api-tokens-part-2

jfdoming/api-tokens-part-1

claude/speed-up-vrt-workflow-ZAyI5

claude/crdt-version-auto-publish-Ph1BH

copilot/add-repository-configs-to-packages

worktree-compressed-drifting-ritchie

worktree-mellow-strolling-dawn

matiss/browser-api

claude/api-consumer-verification-kfz1K

feature/enable-banking

cursor/transaction-table-rewrite-f077

pr-7454

claude/fix-issue-7410-LLLQ4

release/v100.0.0

revert-7350-trim-deps

revert-7220-sankey-report

revert-7242-fix/split-parent-update-corruption

revert-7281-generate-icons

claude/electron-to-tauri-migration-LjBN8

worktree-remotion

release/vv26.4.0-pre

claude/browser-compatible-api-QbhHh

claude/improve-cli-transactions-waTUY

claude/publish-react-native-ios-j8qoT

js-proxy

claude/fix-flaky-ci-job-5gDdz

react-query-rules

react-query-useSchedules

claude/nightly-theme-validation-scan-DzOGD

claude/debug-simplefin-error-ZuKzB

matiss/desktop-client-subpath-imports

claude/fix-simplefin-ssrf-T31gX

claude/release-notes-validation-X7rvR

add-claude-github-actions-1772738270730

cursor/sync-performance-notification-9899

react-query-prefs

matiss/chunked-sync-and-progress-ux

v26.2.1

copilot/sub-pr-6880

fix-react-query-clear-on-close-budget

copilot/sub-pr-6140

feat/auto-note

feat/scoped-bank-sync

cursor/desktop-transactions-react-table-1d0c

fix-exhaustive-deps-App

copilot/fix-find-replace-bug

release/v26.2.0-pre

matiss/browser-tests

mobile-fix-drag-and-drop-across-groups

budget-table-v2

PayeeAutocomplete2

pglite

bugfix/plugins/fix-plugins-sw

feat/plugins/plugins-core-package

prerelease

matiss/unicode-minus-fix

cursor/fix-actual-github-issue-6206-gemini-3-pro-preview-9c37

TransactionFormPage

cursor/implement-mortgage-and-loan-account-type-78ca

tests-update-fill-with-pressSequentially

mobile/link-modal

deps/25.11

cursor/fix-update-vrt-apply-ci-job-dispatch-b324

sync-server-plugins

cursor/propose-patch-for-github-issue-5680-2a18

fix/compiler-preserve-inner-dollar-escapes

cursor/analyze-actual-budget-issue-and-propose-fix-5b70

coderabbitai/docstrings/0c070e5

cursor/add-wip-prefix-and-comment-to-prs-d78d

jfdoming/08-21-auto-focus-on-navigate-in-all-browsers

show-totals-on-mobile-budget-banners

allow-child-transactions-make-transfer

mobile-calculator-keyboard

payee-geolocation

enhance/restore_scroll_position

dm-fix-second-click-on-mobile-new-transaction-2

scrollToLocationBudget

alert-autofix-38

tsconfig-composite

mobile-fix-uncategorized-transactions-on-tracking-budgets

server-budget-handlers

fix-sql-injection-in-cleanup-template

non-chrome-draggable-workaround

mobile-budget-page-swipe-navigation

ts-db-all

stable

dark-theme-with-brand-colors

fix-mobile-delete-group

ts-db-select

UnderKoen/reconcile-context-menu

master-before-server-merge

v25.2.1

ts-runQuery

rename-redux-hooks

UnderKoen/3557-persist-state-in-history

remove-redux-CLOSE_BUDGET

fix-exhaustive-deps-errors-FinancesApp

redux-toolkit-createSlice-backup

accounts-function-component

ts-useSplitsExpanded

loot-core-server-package

useTransactios-in-TransactionEdit

react-aria-input

move-redux-to-desktop-client

QueryState-type

fix-themes-applied-late

mobile-vrts

revert-3295-spendingCardFix

react-aria-button-4

split-payee-on-mobile

twk3/pin-apis-crdt

notes-tag-autocomplete

ts-LoadBackup

dnd-kit

package-upgrades

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/actual#7143