Aman-Mittal opened a new issue, #184: URL: https://github.com/apache/fineract-consumer-facing/issues/184
The repository has a PR template but no issue templates. Bug reports therefore arrive without the details needed to diagnose a BFF failure: the error `code`, the `X-Correlation-ID`, how the stack was run, and the Fineract image. Nothing routes security reports away from public issues, or Fineract Core bugs to Jira. apache/fineract-backoffice-ui has issue forms for bugs and features, plus a config with contact links to the dev list, Matrix and Jira. Its PR template also asks that new features go to [email protected] first. Proposal: - **Bug report form**, asking for: - the area (app or BFF); - steps to reproduce; - the error code and correlation ID; - how the stack was run (e2e compose, JVM, native or dev servers); - the Fineract image and the commit. - **Feature request form**, pointing to the dev list and Matrix first. - **Issue config:** contact links routing security reports to `SECURITY.md` and [email protected], Fineract Core bugs to Jira, and discussion to the dev list and Matrix. - **PR template additions:** - the same dev-list and Matrix guidance; - a security pointer; - checklist items for the backend CQRS and module layout, the frontend adapter boundary, and not growing a lint or architecture baseline. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
