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

dev/core#126 Add support for contact id as a basic report filter. #12172

Merged
merged 1 commit into from
May 21, 2018

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented May 21, 2018

Overview

Re-introduce support for contact id being passed through to the contribution detail report via the url.

This worked in 4.7.29 but regressed in 4.7.30. I think this qualifies as a non-recent regression which means it gets prioritised by the product maintenance team to be fixed but we target the master branch rather than trying to get it into the existing rc (as we would for a recent regression)
This is to address a declared regression https://lab.civicrm.org/dev/core/issues/126 (in 4.7.30) and also to improve flexibility

Before

String in url &force=1&id_op=eq&id_value=34 does not result in filtering

After

Report is filtered (by contact_id = 34) when above url is present. This is the string that is in the url from the soft credit report

Technical Details

Comments

This also exposes contact id as a basic report filter, which I think is a positive by-product

This is to address a declared regression https://lab.civicrm.org/dev/core/issues/126 (in 4.7.30) and also to improve flexibility
@eileenmcnaughton eileenmcnaughton changed the title Add support for contact id as a basic report filter. dev/core#126 Add support for contact id as a basic report filter. May 21, 2018
@colemanw colemanw merged commit e0b8fb0 into civicrm:master May 21, 2018
@colemanw colemanw deleted the report_id_filter branch May 21, 2018 12:01
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