Choosing a JIRA Ticket

O

Qubits of DPK

March 22, 2026

Core Open Source
  1. #
    Look for tickets tagged: gsoc, good-first-issue, help-wanted
  2. #
    Check if the ticket has clear scope (not too vague)
  3. #
    Check if there's already a PR open for it (don't duplicate)
  4. #
    Pick something where you can show a pattern (migration = repeatable work = multiple PRs)
1. Find candidates — grep for RestAssured imports
bash
QUBITS OF DPK
1grep -rl "io.restassured" integration-tests/src/test/java/
This lists every test file still using RestAssured. That's your pool of ~265 files to pick from.
2. Pick easy ones — sort by size
bash
QUBITS OF DPK
1wc -l integration-tests/src/test/java/org/apache/fineract/integrationtests/*.java | sort -n | head -20
Smaller files = fewer dependencies = easier migration.
3. Check if feign client exists for the API being tested
Look at what the test calls. For LoanProductShortNameValidationTest, it calls LoanTransactionHelper which internally posts to /loanproducts. Then check:
bash
QUBITS OF DPK
1grep -n "loanProducts\|LoanProducts" fineract-client/src/main/java/org/apache/fineract/client/util/FineractClient.java
If the field exists in FineractClient.java → feign stub exists → safe to migrate.
4. Check the generated API class for the method
bash
QUBITS OF DPK
1find fineract-client/build/generated -name "LoanProductsApi.java"
2grep -n "def\|Call<" fineract-client/build/generated/.../LoanProductsApi.java
Rule of thumb:
  • Small file + tests a standard CRUD endpoint + feign stub exists = good PR candidate
  • Tests actuator/swagger/legacy-docs endpoints = skip (no feign stub for those)
  • Tests with many Helper dependencies = harder, pick later