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

Add more details to subscription update activity #29564

Merged
merged 1 commit into from
Mar 5, 2024

Conversation

ejegg
Copy link
Contributor

@ejegg ejegg commented Mar 1, 2024

Overview

Adds info about changes in the cycle day or next scheduled contribution date to the activity created when editing a recurring contribution.

Before

If you edit the cycle day and the next scheduled contribution date of a recurring contribution they are not mentioned in the edit activity.

After

If you edit the cycle day and the next scheduled contribution date of a recurring contribution the old and new values are mentioned in the edit activity, e.g.:

Cycle day has been updated from 1 to 16 for this subscription.
Next scheduled contribution date has been updated from to 2024-02-16 for this subscription.

Technical Details

Includes a couple of small cleanup patches

dev/core#5008

Copy link

civibot bot commented Mar 1, 2024

🤖 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...

➡️ Online demo of this PR 🔗

@eileenmcnaughton
Copy link
Contributor

@ejegg style ^^

Include changes to next date and cycle_day.
@ejegg ejegg force-pushed the activityDetails branch from 3c7ddc7 to 998b4cf Compare March 4, 2024 14:34
@mattwire mattwire merged commit 04a1af4 into civicrm:master Mar 5, 2024
3 checks passed
@mattwire
Copy link
Contributor

mattwire commented Mar 5, 2024

Thanks @ejegg we talked about this at the sprint in Montreal. It was felt that either (1) we should not record an activity at all. or (2) more information is always useful.

Because this is just extending existing code by extracting into it's own function I am happy to see this added so I have merged it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants