dev/core#5802 Add option to modify Recurring Membership Contribution when modifying Membership Type

[shaneonabike]

Overview

We have a situation where Members transition from one type to another. We recently setup recurring memberships, but are running into the scenario that the recurring payments are not updated.

I'm aware that there are reasons that some don't want this done automatically, which is totally fine with me. But I was wondering if we couldn't provide a checkbox allowing the update to happen since I feel that it makes sense to provide out-of-the-box.

Example use-case

1. Member uses a Contribution page and pays for a Recurring Membership
2. Member contacts the Organization to have their Membership changed to another one
3. The organization goes to the Members page and attempts to change their Membership
4. They override the Membership but the recurring transaction still charges the original amount

Current behaviour

Proposed behaviour

We provide the option to allow them to update the actual next recurring amount. I can see there is already a place that we could handle this and modify the Recurring contribution amount with the new total amount.

Comments

I already implemented the UI to handle this, but wanted to ensure there wasn't something I am missing here in terms Payment Processors prior to proposing a patch.

[civibot]

🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷

Introduction for new contributors...

• If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
• A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
• A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
• If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
• Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
• A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
• To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
• For more information about contributing, see CONTRIBUTING.md.

Quick links for reviewers...

• ➡️ PR Demo site (can be rebuilt with the command test this please).
• 📖 Review standards
• 🗒️ Review template (brief or verbose)

➡️ Online demo of this PR 🔗

[civibot]

The issue associated with the Pull Request can be viewed at https://lab.civicrm.org/dev/core/-/issues/5802

[shaneonabike]

I updated the ticket but I think I will close this since @mattwire pointed me to some extensions that get me most of the way there. I think if we want to expand that functionality via the extensions that could be a good approach. Also, we should probably document this to help people b/c I could see it as a deterrent in adoption.