From 487418e23ada1b27b96f806800d4e62007296ab8 Mon Sep 17 00:00:00 2001 From: Andrew Hunt Date: Wed, 7 Mar 2018 14:56:58 -0500 Subject: [PATCH] 4.7.31 release notes: fixed one mis-categorized thing --- release-notes/4.7.31.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/release-notes/4.7.31.md b/release-notes/4.7.31.md index 7aa6a89465..7534b52f47 100644 --- a/release-notes/4.7.31.md +++ b/release-notes/4.7.31.md @@ -160,6 +160,13 @@ Released March 7, 2018 When saving an address using the API, you can now bypass a handful of fixes that normally get applied. +- **[CRM-21741](https://issues.civicrm.org/jira/browse/CRM-21741) For in-place + editing, allow data-params to be passed to CRM.api3 + ([11639](https://github.com/civicrm/civicrm-core/pull/11639))** + + Fields enabled for in-place editing can now specify additional API parameters + to be sent when saving updates. + ### CiviCampaign - **[CRM-21593](https://issues.civicrm.org/jira/browse/CRM-21593) New order by @@ -169,13 +176,6 @@ Released March 7, 2018 The Walk / Phone List Report now can be sorted by street name, street number, and whether the street number is odd or even. -- **[CRM-21741](https://issues.civicrm.org/jira/browse/CRM-21741) For in-place - editing, allow data-params to be passed to CRM.api3 - ([11639](https://github.com/civicrm/civicrm-core/pull/11639))** - - Fields enabled for in-place editing can now specify additional API parameters - to be sent when saving updates. - ### CiviCase - **[CRM-21461](https://issues.civicrm.org/jira/browse/CRM-21461) Case Dashlet -- 2.25.1