[
https://issues.apache.org/jira/browse/FINERACT-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Foo Developer updated FINERACT-2683:
------------------------------------
Description:
The GET /v1/makercheckers endpoint has two filter issues:
1. Date filters non-functional — makerDateTimeFrom / makerDateTimeTo query
parameters filter against the made_on_date column, but records created after
the UTC-offset migration
are stored in made_on_date_utc. This makes date-range filters return no
results for any entry created since the migration. The fix applies the same
OR-pattern already used by
AuditsApiResource: check both made_on_date and made_on_date_utc so the
endpoint works correctly regardless of which column a given record uses.
2. Username filter missing — there is no way to filter maker-checker entries
by the maker's username. The mk (appuser) table is already joined in the
underlying query; this adds a username query parameter and a LIKE filter
against mk.username.
was:
h2. *Checker Inbox Filters Not Functioning (Date, Resource ID, Entity, Action)*
On the *Checker Inbox & Tasks* page, multiple filtering functionalities are not
working as expected.
> Fix date and username filters on Maker-Checker inbox endpoin
> -------------------------------------------------------------
>
> Key: FINERACT-2683
> URL: https://issues.apache.org/jira/browse/FINERACT-2683
> Project: Apache Fineract
> Issue Type: Bug
> Components: Organization
> Reporter: Foo Developer
> Priority: Major
>
> The GET /v1/makercheckers endpoint has two filter issues:
>
>
>
>
>
> 1. Date filters non-functional — makerDateTimeFrom / makerDateTimeTo query
> parameters filter against the made_on_date column, but records created after
> the UTC-offset migration
> are stored in made_on_date_utc. This makes date-range filters return no
> results for any entry created since the migration. The fix applies the same
> OR-pattern already used by
> AuditsApiResource: check both made_on_date and made_on_date_utc so the
> endpoint works correctly regardless of which column a given record uses.
>
> 2. Username filter missing — there is no way to filter maker-checker
> entries by the maker's username. The mk (appuser) table is already joined in
> the underlying query; this adds a username query parameter and a LIKE filter
> against mk.username.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
