Skip to content

Slightly confusing UX with recurring expenses #699

Description

@phobiac

Describe the bug
In investigating #698 I noticed a few things in the recurring expenses UI that I wanted to note. These may be better as separate issues but I wasn't sure where the line is as they are all interconnected.

Firstly, I noticed that the message you are given when editing a recurring expense is different if you editing the first instance or a schedule created one (see the first 2 screenshots)

Second, when clicking on a recurring expense in the /recurring endpoint it links to the most recently created expense. In this case I get the second message with the link back to the recurring endpoint. I am not sure if this is intended or if it should be linking back to the first expense (assuming editing the first one changes all following expenses).

Third, it's slightly unclear what the result of editing the initial expense is. While the first message notes that it will "apply to future recurring expenses", I did a test edit of the first expense in a recurring expense chain and it did not change the value of the expense created after it that already existed. I assume it only changes any expense newly created after that edit?

Screenshots

Result when editing the first expense in a recurring expense, no link to the recurring transactions view
Image

Result when editing a CRON created recurring expense
Image

App version
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:152.0) Gecko/20100101 Firefox/152.0
Git: f0ca6d9
Version: v2.1.4

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions