github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 19:52:56 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #268] [CLOSED] Add support for customizing schedule names #3087

New Issue
Closed
opened 2026-02-28 20:36:06 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:36:06 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/268
Author: @j-f1
Created: 10/7/2022
Status: ❌ Closed

Base: master ← Head: named-schedules

📝 Commits (3)

  • 3945a71 Change schedule table to show “Any” rather than “None”
  • 214db89 Add support for customizing schedule names
  • 0cb49fa WIP: undo schedule name, try storing name as notes field in action

📊 Changes

8 files changed (+59 additions, -9 deletions)

View changed files

📝 packages/desktop-client/public/data-file-index.txt (+2 -1)
➕ packages/desktop-client/public/data/migrations/1665591426587_schedule_notes.sql (+5 -0)
📝 packages/desktop-client/src/components/schedules/EditSchedule.js (+28 -2)
📝 packages/desktop-client/src/components/schedules/SchedulesTable.js (+7 -3)
📝 packages/desktop-client/src/components/util/DisplayId.js (+8 -3)
➕ packages/loot-core/migrations/1665591426587_schedule_notes.sql (+5 -0)
📝 packages/loot-core/src/server/aql/schema/index.js (+2 -0)
📝 packages/loot-core/src/server/migrate/migrations.js (+2 -0)

📄 Description

This renames the “Payee” column of the schedule editor to “Name” and allows overriding the payee with a custom name. This is useful if you want to track several subscriptions payable to the same account (for example, I have several subscriptions paid via Apple for different apps, but want to label them with the actual recipient of the funds).

Are there any places I’m missing where we call out a schedule name that need to be updated too?

An open design question is where exactly the text field should be placed — I don’t really like either of these implementations:

Screenshot_2022-10-07 15 39 09 Screenshot_2022-10-07 15 45 44

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/268 **Author:** [@j-f1](https://github.com/j-f1) **Created:** 10/7/2022 **Status:** ❌ Closed **Base:** `master` ← **Head:** `named-schedules` --- ### 📝 Commits (3) - [`3945a71`](https://github.com/actualbudget/actual/commit/3945a71b6f19ba52947a602b8961c2086cc0c112) Change schedule table to show “Any” rather than “None” - [`214db89`](https://github.com/actualbudget/actual/commit/214db89cbbce1032e698facc7753094ad556172c) Add support for customizing schedule names - [`0cb49fa`](https://github.com/actualbudget/actual/commit/0cb49fa98f0948c92fdcd53aa0159f4f7a6cb543) WIP: undo schedule name, try storing name as notes field in action ### 📊 Changes **8 files changed** (+59 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/public/data-file-index.txt` (+2 -1) ➕ `packages/desktop-client/public/data/migrations/1665591426587_schedule_notes.sql` (+5 -0) 📝 `packages/desktop-client/src/components/schedules/EditSchedule.js` (+28 -2) 📝 `packages/desktop-client/src/components/schedules/SchedulesTable.js` (+7 -3) 📝 `packages/desktop-client/src/components/util/DisplayId.js` (+8 -3) ➕ `packages/loot-core/migrations/1665591426587_schedule_notes.sql` (+5 -0) 📝 `packages/loot-core/src/server/aql/schema/index.js` (+2 -0) 📝 `packages/loot-core/src/server/migrate/migrations.js` (+2 -0) </details> ### 📄 Description This renames the “Payee” column of the schedule editor to “Name” and allows overriding the payee with a custom name. This is useful if you want to track several subscriptions payable to the same account (for example, I have several subscriptions paid via Apple for different apps, but want to label them with the actual recipient of the funds). Are there any places I’m missing where we call out a schedule name that need to be updated too? An open design question is where exactly the text field should be placed — I don’t really like either of these implementations: <img width="772" alt="Screenshot_2022-10-07 15 39 09" src="https://user-images.githubusercontent.com/25517624/194641791-ef5b678c-81ea-4ceb-8c40-3c23fa4bbad8.png"> <img width="767" alt="Screenshot_2022-10-07 15 45 44" src="https://user-images.githubusercontent.com/25517624/194641803-ad4aa8d1-aea8-40eb-847c-6ec75b0d69cd.png"> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 20:36:06 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#3087
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?