Skip to content

Conversation

@somasorosdpc
Copy link
Contributor

Description

Describe the changes made and why they were made.

Ignore if these details are present on the associated Apache Fineract JIRA ticket.

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Write the commit message as per https://github.com/apache/fineract/#pull-requests
  • Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
  • Create/update unit or integration tests for verifying the changes made.
  • Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
  • Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
  • Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@adamsaghy
Copy link
Contributor

@somasorosdpc Please rebase and check the failing test cases.

@somasorosdpc somasorosdpc force-pushed the FINERACT-2354/chargeback-handling-with-re-age-for-equal-amortization-re-aging-behaviour branch 7 times, most recently from d395ace to ba229a2 Compare November 27, 2025 13:56
@adamsaghy
Copy link
Contributor

@somasorosdpc Please rebase

…t adjustment strategy with equal amortization re-aging behaviour
…ted re-age for last adjustment strategy with equal amortization re-aging behaviour
@somasorosdpc somasorosdpc force-pushed the FINERACT-2354/chargeback-handling-with-re-age-for-equal-amortization-re-aging-behaviour branch from ba229a2 to 127871f Compare December 5, 2025 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants