Dear newcomer, we kindly request that you begin your onboarding by reviewing our curated, helpful information under this link: https://issues.apache.org/jira/browse/FINERACT-2135
Every contribution that enhances the codebase’s safety, effectiveness, or readability is valuable! :) Considering your availability and willingness to contribute, there are several areas where improvements are needed: Bug tickets https://issues.apache.org/jira/browse/FINERACT-2492?filter=-1&jql=project%20%3D%20%22Apache%20Fineract%22%20%20AND%20type%20%3D%20Bug%20%20%20AND%20resolution%20%3D%20Unresolved%20order%20by%20created%20DESC Code maintainability / readability We have a significant number of compilation warnings due to various reasons. I believe at least half of these warnings could be easily fixed. As we work on resolving these warnings, the codebase could become safer and easier to maintain. All the rest of the stories https://issues.apache.org/jira/browse/FINERACT-2494?filter=-1&jql=project%20%3D%20%22Apache%20Fineract%22%20%20AND%20resolution%20%3D%20Unresolved%20order%20by%20created%20DESC All the rest of the stories that are considered beginner friendly https://issues.apache.org/jira/browse/FINERACT-2489?filter=-1&jql=project%20%3D%20%22Apache%20Fineract%22%20and%20labels%20IN%20(beginner-friendly%2C%20beginner%2C%20begineer%2C%20beginners%2C%20Beginner)%20%20AND%20resolution%20%3D%20Unresolved%20order%20by%20created%20DESC Hopefully, this gives you some ideas! P.S.: Before you pick up a story that describes a new feature to be introduced, please send an email to the Fineract DEV email list to discuss whether it’s something we really want to include in Fineract. Regards, Adam > On Oct 14, 2026, at 6:41 PM, Mandib Chaulagain <[email protected]> > wrote: > > Hi all, > I'm Mandib, a backend developer. While upgrading an installation from 1.14.0 > to 1.15.0 on PostgreSQL, I found that deactivating a charge fails with > "operator does not exist: boolean = integer". It also reproduces on current > develop. Looking at the history, this bug has been there since 1.7.0, the > first release that supported PostgreSQL. > Ticket: https://issues.apache.org/jira/browse/FINERACT-2951 > PR: https://github.com/apache/fineract/pull/6656 > The fix removes a leftover "=1" in one query, matching its sibling queries, > and adds an integration test that deactivates a charge. > As this is my first PR, the CI workflows need a maintainer's approval to run. > I'd appreciate it if someone could approve them and review. My JIRA username > is cmandib, for when the Contributor role becomes relevant. > Thanks, > Mandib.
