Currently, it's really hard to track all the different events related to the subscription.
I'm thinking a great way to improve the clarity here would be to introduce an activity log, similar to orders.
We probably should make this optional by putting this functionality in a commerce_recurring_log submodule (with a dependency on commerce_log).
We should start by recording the following events:
RecurringOrderManager::renewOrder()). RecurringOrderManager::closeOrder())?order_state_updated and an event subscriber reacting to commerce_subscription.post_transition.Active
1.0
Code
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
A new patch has been added that includes logs on the subscription entity. The logs are now visible on the edit subscription page.
As part of this issue, I created a new module Commerce Recurring Log → to enhance logging and traceability of recurring subscriptions in the system.