[Docs] .github/ISSUE_TEMPLATE/bug_report.md does not prompt for FlowFi environment (backend/frontend/contracts) or network (testnet/mainnet)

[grantfox-oss]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

.github/ISSUE_TEMPLATE/bug_report.md is a generic bug template. FlowFi spans three sub-projects (backend, frontend, contracts) and two Stellar networks (testnet, mainnet/futurenet). Without a field asking which component and network a bug affects, triagers have to ask this in every thread before they can even route the issue.

Acceptance criteria

• Add a "Component" field/checkbox (backend / frontend / contracts / infra)
• Add a "Network" field (testnet / mainnet / local sandbox)
• Verify the rendered template on GitHub's new-issue picker

Files to touch

• .github/ISSUE_TEMPLATE/bug_report.md

Out of scope

• Converting to YAML issue forms
• Changing the feature_request or security templates

[EstherIkechukwu]

I have gone through the description expect a pr in less than 24hrs

[Fury03]

@Fury03 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i can work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Fury03 to this issue.

[OpensrcLord]

@OpensrcLord has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello @maintainer, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me. And I will deliver at the shortest possible time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OpensrcLord to this issue.

[CHKM001]

@CHKM001 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i WOULD LOKE TO GET THIS DONE AND COMPLETE THIS DOC AS WELL
PR within 3 hrs as well
Than you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CHKM001 to this issue.

[abdulqoyumadegoke]

@abdulqoyumadegoke has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi team! 🦊 I'm ready to tackle this task. My technical background aligns well with this issue, and I can have a clean, tested Pull Request ready for review within your expected timeframe. Please let me assign me so I can begin

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abdulqoyumadegoke to this issue.

[Hikmaholadele]

@Hikmaholadele has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer, I’d love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hikmaholadele to this issue.

[mayborn005]

@mayborn005 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mayborn005 to this issue.

[drips-wave]

Congratulations, @abdulqoyumadegoke! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @abdulqoyumadegoke: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊