See https://docs.google.com/spreadsheets/d/17Pc1tIvqol6XJhuu97RlOfwy_Avbb9MEaRwhy2F529I/edit?gid=292544213#gid=292544213
This is a native amount fields paired with a date field that is set whenever the corresponding field is changed
Minor note: We are only calculating changes within the same recurring contribution (amount upgraded or downgraded), we aren't including situations where the donor cancels one donation and creates a new one with a different amount.
Change #1306984 had a related patch set uploaded (by Lars SG; author: Lars SG):
[wikimedia/fundraising/crm@master] Add last_recurring_amount_change and accompanying change date fields
Change #1306984 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Add last_recurring_amount_change and accompanying change date fields
Change #1308708 had a related patch set uploaded (by Lars SG; author: Lars SG):
[wikimedia/fundraising/tools@master] Add last_recurring_amount_change & date to Acoustic export
Change #1308708 merged by jenkins-bot:
[wikimedia/fundraising/tools@master] Add last_recurring_amount_change & date to Acoustic export
Change #1309723 had a related patch set uploaded (by Lars SG; author: Lars SG):
[wikimedia/fundraising/crm@master] Backfill last_recurring_amount_change and date
Noting here that past recurrings that were cancelled or failed in 2022 (Jul-Nov?) appear to have amount changes because we somehow changed the amount of the recur at that point to the USD amount, replacing the native currency amount. So these changes aren't real and we'll ignore all changes before 2024 (I don't see any before then that are real).
Change #1309723 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Backfill last_recurring_amount_change and date
Change #1310209 had a related patch set uploaded (by Lars SG; author: Lars SG):
[wikimedia/fundraising/crm@master] Prevent db lock on upgrade 5050 read
Change #1310209 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Prevent db lock on upgrade 5050 read