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

[Bug]: Schedule icon shows up on add transaction row when there is a due schedule with no payee #1616

Open
1 task done
joel-jeremy opened this issue Aug 31, 2023 · 1 comment · May be fixed by #4267
Open
1 task done
Labels
bug Something isn't working help wanted Extra attention is needed schedules Related to schedules transactions Related to transactions

Comments

@joel-jeremy
Copy link
Contributor

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Steps to reproduce:

  1. Create a schedule that is due and assign to an account
  2. Leave payee field empty
  3. Add new transaction to the account used in step 1 and set its payee

image
image

What error did you receive?

No response

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

@joel-jeremy joel-jeremy added bug Something isn't working help wanted Extra attention is needed schedules Related to schedules transactions Related to transactions labels Aug 31, 2023
@lelemm
Copy link
Contributor

lelemm commented Oct 24, 2024

Is this a bug or working as intended?
the schedule icon appeared because the value of the schedule is the same as the new transaction (zero).

If you try the same with a schedule with a value, it doesn't happen until you set a value equal:
image

as soon as set the value to the same as the schedule:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed schedules Related to schedules transactions Related to transactions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants