Details
-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 4.6.14
-
Fix Version/s: Unscheduled
-
Component/s: CiviContribute
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:User and Admin Doc
-
Funding Source:Contributed Code
Description
This is a case I requested comment from Eileen McNaughton on:
"So we don't get what turns out to be rubbish stored against recurring contributions can we alter the recurring transaction process so the source and page id do not show the details from the original transaction?
The source could be set to default to something like "Recurring Contribution Processed"
Eileen's comment:
"I found where to change it in the code - but can you log a JIRA explaining why - it has been set fairly intentionally and I'm not 100% sure if this is right as a core-codebase change or not - I need to see people's response I guess.
I wonder if the description should also include the recurring contribution ID and / or the payment processor name - adding those seems to impart useful info to me"
My response to the suggestion for recurring id and payment processor is that the first is stored as part of the contribution record and the second is stored as party of the recurring transaction record so I don't see these necessarily being useful being stored in the source field of the contribution record.
Comments from others?