Help Inbox shows raw internal ID (rec:1323) - replace with readable context

[Ayush-Patel-56]

Problem

Help Inbox messages show a raw internal string like rec:1323 which is meaningless to the user. This appears to be the recommendation ID leaking into the UI.

Steps to reproduce

1. Go to Help Inbox
2. See the text rec:1323 below the mentee's message

Expected behavior

This field should either:

• Not be shown at all, or
• Be replaced with something readable like the issue title or repo name

Implementation notes

• The rec:ID appears to be a tag/identifier stored on the help request
• Either strip it from the displayed message or resolve it to the issue title before rendering
• File: src/app/(app)/help-inbox/page.tsx

[Ari-Han-t]

Hi @Ayush-Patel-56 I am an independent developer, not yet associated with GSSOC, but I still want to contribute, please assign this issue to me.

[Anushka904]

Hi @Ayush-Patel-56, I noticed this bug was just opened and would like to take it up. Internal identifiers like rec:1323 surfacing in the UI is a data rendering issue that needs a clean fix rather than a workaround.

My approach would be to examine the help-inbox page component, trace how the help request data flows into the rendered message, and ensure the rec:ID field is either filtered out or mapped to a human-readable value such as the issue title before the component renders.

Would love to be assigned this one under GSSOC26. Thanks!

[Soumya-codr]

@Ari-Han-t Assigned u and please note if u are not. in GSSOC , also u can contribute dont worry

Happy Coding

[Soumya-codr]

Hi @Anushka904,

Thank you for your interest and the detailed approach! It is a great breakdown of the problem.

As this issue has already been assigned to @Ari-Han-t, you are welcome to collaborate with them on this if they are open to it. Alternatively, please feel free to look for and take up other open issues in the repository.

We appreciate your support and enthusiasm! Happy coding!

Sorry once again but Happy Coding😊

[Ari-Han-t]

Hi @Soumya-codr and @Ayush-Patel-56 I create a Pull Request for the fixed issue, can a maintainer please review and hopefully accept my PR, to fix this issue, thankyou so much, this will be my first OPENSOURCE contribution to a large repository like MergeShip.

[omkartike]

i would like to work on this issue under nsoc , if possible assign me

[Soumya-codr]

Hi @Soumya-codr and @Ayush-Patel-56 I create a Pull Request for the fixed issue, can a maintainer please review and hopefully accept my PR, to fix this issue, thankyou so much, this will be my first OPENSOURCE contribution to a large repository like MergeShip.

kindly link the PR with this issue since we are not getting the PR for this issue