Creating a subscription no longer opens a pre-filled rule editor since 6.7.0

Support guidelines

• I'm smart and I read the support guidelines

Use of AI

• I'm a real person and wrote this bug without assistance from AI.

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem
• ... it's definitely a Firefly III issue, not me

Description

Since upgrading from Firefly III 6.6.6 to the 6.7.x releases, I noticed a change in the workflow when creating a new subscription.

In Firefly III 6.6.6 and earlier, after creating a new subscription, Firefly III automatically opened the editor for creating a corresponding rule. The rule was already pre-filled with information from the newly created subscription, such as the description and amount.

This made it very easy to create a rule that automatically linked matching transactions to the subscription.

Since 6.7.0, this no longer seems to happen.

Debug information

N/A

Steps to reproduce

1. Create a new subscription.
2. Enter a description and an expected amount.
3. Save the subscription

Additional info

Previous behavior (6.6.6)

After saving the subscription, Firefly III automatically opened the rule editor.

The new rule was already pre-filled with information from the subscription, including relevant fields such as the description and amount. This made it possible to review the generated rule and save it with only minor adjustments if necessary.

Current behavior (6.7.x)

After saving the subscription, no pre-filled rule editor is opened.

Instead, a rule has to be created manually afterwards. The conditions have to be entered manually as well, and the rule then has to be manually linked to the subscription.

Expected behavior

I would expect the previous workflow to remain available: after creating a subscription, Firefly III should open the rule editor with a new rule pre-filled from the subscription.

Since this functionality was present in 6.6.6 and disappeared with the 6.7.x releases, I am not sure whether this is an intentional change related to the new UI or a regression.