Skip to content

bug: Investment history pagination breaks when filtering by status — next/prev buttons don't work #471

Closed

Description

@sshdopey

Problem

Filter by 'pending' status, then click next page, returns to unfiltered list.

Activity

  1. Fhatu12 commented on Sep 1, 2026

    @Fhatu12
    Contributor

    Hi, I'd like to work on this issue. I’ll keep the fix focused on preserving the active investment-history status filter across next/previous pagination navigation, add regression coverage for the filtered pagination flow, and avoid unrelated portfolio/history refactors. Please assign me before I proceed.

  2. Genesis000001 commented on Sep 30, 2026

    @Genesis000001

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

    Good day maintainer,I have gone through the description and I would like to work on this issue please assign

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

  3. collins-uzu commented on Sep 30, 2026

    @collins-uzu

    @collins-uzu has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hi, I’ve reviewed the issue and understand the requirements. I have the skills needed to work on it and would be happy to take it up. Please assign it to me.

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

  4. Hakimi674 commented on Sep 30, 2026

    @Hakimi674

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

    I’d be happy to contribute to this issue. After reviewing the requirements, I understand the changes expected and am prepared to implement them. Please consider assigning the issue to me.

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

  5. johnmic0132 commented on Sep 30, 2026

    @johnmic0132

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

    Hello Maintainer, I’d love to take on this issue.
    Kindly assign it to me.

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

  6. Xhaka00 commented on Sep 30, 2026

    @Xhaka00

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

    Hi maintenance,I would be glad if I can work on this ,wave is ending soon

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

  7. Bollywere commented on Sep 30, 2026

    @Bollywere

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

    Hello, I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it.

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

  8. Ajibola6921 commented on Sep 30, 2026

    @Ajibola6921

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

    I can handle this issue and will like to work on it, Please assign thank you.

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

  9. Nwapu-TrustJah commented on Sep 30, 2026

    @Nwapu-TrustJah

    @Nwapu-TrustJah has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hi Maintainer,​I can resolve this pagination state issue. I'll modify the investment history table state and query parameter handling in Heliobond/frontend so next/prev navigation retains all active filter criteria, and verify the fix with unit/component tests. Feel free to pass this over to me!

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

  10. PEPPERITO23 commented on Sep 30, 2026

    @PEPPERITO23
    Contributor

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

    I understand the expected outcome and would love to work on this. I'll provide a solution that satisfies the acceptance criteria.

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

  11. drips-wave commented on Sep 30, 2026

    @drips-wave

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

    🧑‍💻 @PEPPERITO23: 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 🌊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions