Is it possible to have other type of relationship amongst issues, besides the "parent/child" one?

[JacopoDioBrando]

Select Topic Area

Question

Feature Area

Issues

Body

The only relationship I can find for issues is this one:

The GitHub parent relationship

I'd like to specify instead other kind of relationship amongst issues in GitHub.
For example I need to link issues that are just related, but not strictly children of another issue.
Or it would be more explicit to assign an "affects" relationship to a user story caused by a bug. Coming from tools like Azure DevOps and Jira I miss that kind of flexibility.

Did I miss something, is there any kind of workaround, external plugin/tool or future feature in roadmap that would fit my need?

I know you can link issues amongst each other, but the problem is that relationship is not specified so you have to be verbose in the description, whilst it would be easier to just choose the right relationship creating an issue and then it would be easier also to have, for example, a dependencies overview of the project.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[bobeagan]

Looks like it was bumped to next quarter github/roadmap#1076

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[nh-mmulders]

Well-phrased @JacopoDioBrando.
I really miss this functionality and like to have it, also coming from Azure DevOps.
For example: when a bug is found and reported as an issue in our GitHub project, it is often essential to be referred to the original requirement to understand and fix the bug.