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.

Sign up for GitHub

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

Jump to bottom

CRM-20950 Prt 2 Contact import mapping to wrong location type #10736

Merged
merged 1 commit into from
Jul 24, 2017
Merged

CRM-20950 Prt 2 Contact import mapping to wrong location type #10736

merged 1 commit into from
Jul 24, 2017

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Jul 24, 2017 •
edited by civicrm-builder
Loading

@eileenmcnaughton
Copy link
Contributor Author

@monishdeb didn't click too hastily here :-) - I think with this one sanity is restored. Yay for longer rc cycles

@monishdeb
Copy link
Member

Yup it worked.

@monishdeb monishdeb merged commit 7e38353 into civicrm:4.7.23-rc Jul 24, 2017
@eileenmcnaughton eileenmcnaughton deleted the reg branch July 24, 2017 12:34
eileenmcnaughton added a commit to eileenmcnaughton/civicrm-core that referenced this pull request Feb 1, 2018
@eileenmcnaughton
CRM-20950 Contact import mapping to wrong location type
791d0ff 
This incorporates PRs

civicrm#10736

and

civicrm#10735

Which fix a mistake (not in a stable CiviCRM release) from my earlier primary address
update. This causes the bug where Leanne is saying addresses are going to
old 2014 rather than old 2017

Bug: T169025

Change-Id: Ida5ad1a7564b3233b8fb4c75b8d56a46447e1a98
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
4.7.23-rc
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@eileenmcnaughton @monishdeb @civicrm-builder