Apologies, meant to address the mail to Santosh :) Regards, Vishwas
On Tue, May 28, 2019 at 9:29 PM Vishwas Babu < [email protected]> wrote: > Sampath, > > Angel has raised this issue at FINERACT-757 . The fix for the same has > been cherry-picked into the 1.3.1 branch. Can you please test it out and > ship it as a part of the 1.3.1 patch release? > > Regards, > Vishwas > > > > On Wed, May 22, 2019 at 1:49 PM Angel Cajas <[email protected]> wrote: > >> Hi Awasum. >> >> >> >> Thanks for your response, I will create the issue and ask for your review >> after fixing it. >> >> >> >> >> >> *From:* Awasum Yannick <[email protected]> >> *Sent:* miércoles, 22 de mayo de 2019 12:30 >> *To:* Dev <[email protected]> >> *Subject:* Re: Client retrieval endpoint fix >> >> >> >> Hi Angel, >> >> >> >> Create an issue ASAP. If you are convinced its a problem, create an issue >> and fix it. >> >> If it turns out to be a false alarm, you can always close the issue again. >> >> >> >> Thanks for investigating. >> >> >> >> On Wed, May 22, 2019 at 4:52 PM Angel Cajas <[email protected]> >> wrote: >> >> Hi everyone. >> >> >> >> Recently I’ve been testing the client retrieval endpoint sending a GET >> request to the path “/fineract-provider/api/v1/clients” and noticed >> that when you provide extra parameters to the search like firstName or >> lastName the result is empty. Should I create an issue in Jira by myself >> and fix it? Or is someone in charge of reviewing the problem described >> before creating the issue? >> >> >> >> Regards, Angel >> >>
