[Bot] Add Automated Bug Reporting in /feedback

[Solomonsolomonsolomon]

Enhance the feedback command to automatically capture and forward technical bot issues to the development team.nn- Priority: Low

[dhareymu]

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

Hi moderator. I would like to fix this issue. Kindly assign it to me. Thank you

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

[gelluisaac]

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

I’m interested in tackling this! I have a strong background in smart contract development and full-stack systems, so I'm well-equipped to handle the requirements here. Could you please assign this to me?

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

[samuelisi]

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

I’m a Smart Contract Developer who transforms complex concepts into secure, scalable, and production-ready blockchain solutions.

Specializing in Rust and Solidity, I build smart contracts that are efficient, reliable, and designed with security at their core. With hands-on experience using the Stellar SDK, I develop Web3 applications that move real value and solve real-world problems.

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

[legend-esc]

@legend-esc has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue because automatically deactivating expired campaigns is an important consistency and reliability improvement that prevents stale campaigns from remaining active indefinitely in both the backend and potentially on-chain state. Automating this process reduces operational overhead, improves data integrity, and ensures frontend users are not presented with expired campaigns as still active.

I have experience implementing background job systems, scheduled maintenance tasks, and blockchain-integrated backend workflows, and I’m comfortable building reliable automation that safely synchronizes off-chain and on-chain state transitions. For this issue, I would focus on extending the existing job runner in backend/src/index.js with a scheduled campaign-expiration task that identifies campaigns whose endDate has passed and automatically marks them inactive in the database.

I would also implement optional on-chain synchronization logic to call set_active(false) when a linked contract exists, while ensuring failures in blockchain interaction do not corrupt backend state or halt the scheduler. Particular attention would be given to idempotency, retry-safe behavior, structured logging, and efficient querying so the job remains safe and performant as campaign volume grows. In addition, I would add tests covering expired campaigns, already-inactive campaigns, missing contract links, and partial-failure scenarios to ensure the automation behaves reliably under real-world conditions.

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

[AkamyUI]

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

Can i work on this issue

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

[tecch-wiz]

@tecch-wiz has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I'd like to work on this issue. I have experience in software development and would be happy to contribute. Could you please assign it to me?

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