GitHub Community
Add relation between issues #4928
Replies: 14 comments 11 replies
-
|
I'm also looking for this. Not so much issue dependency, but using issues for both tasks that get completed, and to track user needs over time. For example, let's say you use a repository to track job stories, jobs to be done, or any flavor of user outcomes that you continuously address. You also have a repository with code and normal issues that get completed per release, sprint, task, etc. I'm wanting issues to be related to other issues as a named relationship. For example, development tasks are issues that have a custom relation property named "Addresses" where you are able to select one or many job story issues. In the new table view, you could see which user outcomes are being addressed in each development task. Or you could have a project view with the inverse so you could primarily view the job story issues and which development tasks are addressing each job story. Custom relations are what make Notion and Airtable so powerful, with the downside of them being separate system of records from where the work is getting done - GitHub. Unless I'm missing something, per the marketing page, how are relationships getting tracked? Or is it just currently issues referencing other issues in their timelines? If so, that's great as an audit trail, but not so great for product planning / management.
|
Beta Was this translation helpful? Give feedback.
-
|
I came here to either upvote or request this myself. We currently use Shortcut (formerly Clubhouse) for the bulk of our ticket management, but I would love to be able to migrate the team at some point in the future. Shortcut has the ability to add related issues and designate a particular type in the relation (related/blocking/blocked by/duplicates/duplicated by). All related issues are then grouped into a neat list for reference (similar to linked PRs in GitHub's side bar)
|
Beta Was this translation helpful? Give feedback.
-
|
An idea to consider would be to add a field type (next to |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
This is a key missing feature for me as well. Since projects can span multiple repositories, one should also be able to mark an issue as dependent on an issue in another repository. |
Beta Was this translation helpful? Give feedback.
-
|
Exactly also looking for this! |
Beta Was this translation helpful? Give feedback.
-
|
I'm also looking for this! |
Beta Was this translation helpful? Give feedback.
-
|
Hey folks! We're working on a more robust implementation of precisely this! For now, you can use Task lists for this functionality: https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists |
Beta Was this translation helpful? Give feedback.
-
|
I think that may cover some scenarios, but not all. For instance, I may want to link an issue specifically to its "Parent" issue. So being able to have a custom field type of 'issue' for instance and let me select/link to an issue as a value of that field would be great for that. But it may also just be a list of other random PRs/issues/discussions that I want to track as 'related'. A task list may cover that but has to live in the issue somewhere vs. just being part of the project board the team uses. |
Beta Was this translation helpful? Give feedback.
-
|
@omerbensaadon any update? |
Beta Was this translation helpful? Give feedback.
-
|
👋 @omerbensaadon same question as above - is there any update? Even if this is no longer being looked at it would be good to know that's the case. Echoing the above I think this would offer real value. This is something our product/delivery managers expect if they migrate from JIRA or ZenHub. |
Beta Was this translation helpful? Give feedback.
-
|
This is a blocked beta that is not accepting new users, so maybe this will not fix the requirement |
Beta Was this translation helpful? Give feedback.
-
|
@omerbensaadon can you give an update on the plans beyond task lists? The "For now" is 1.5 years old |
Beta Was this translation helpful? Give feedback.
-
|
As far as I understand task lists do not allow the definition of specific relationships, they are just links in the text. |
Beta Was this translation helpful? Give feedback.
-
|
I generally find myself going to two separate issues and having them reference each other to get the nice link to appear in the feed of each: This doesn't scale well beyond linking two issues together. Especially, as it's one sided, if someone just mentions an issue in their comment like this:
It only gets visibility more on the feed of the other linked issue:
It'd be really nice for the side panel to have a complete list of issues that are referencing this one and that this one references: For the above example, from this issue, I would just have a summary and see a list of related issues something like:
|
Beta Was this translation helpful? Give feedback.
-
|
I'm also looking for this feature. Is the GitHub product team monitoring this discussion? It seems that this issue has been outstanding for quite some time, yet the feature still doesn't exist. |
Beta Was this translation helpful? Give feedback.
-
|
Issue dependencies have been requested since 2014 with no real movement, unfortunately. |
Beta Was this translation helpful? Give feedback.
-
|
It seems interesting to learn that the Projects and Issues team is considering adding a 'dependency' to an issue. |
Beta Was this translation helpful? Give feedback.
-
|
Issue relationships are important for projects of any size. If I have an issue that can't be completed due to a dependency on a different issue. I have no way of linking those together other than "mentioning" it in the comments. Tracking these isn't possible. I think a good example of a good way to implement an issue tracker is JIRA, the platform is more advanced but the simplicity of linking issues is something GitHub would benefit from, especially for smaller projects. The growth of the projects is being held back by this very simple feature. |
Beta Was this translation helpful? Give feedback.
-
|
If the product team needs inspiration on how this could/might work, Linear does a beautiful job of managing relationships between tickets. |
Beta Was this translation helpful? Give feedback.
-
|
GitLab supports this, as https://gitlab.com/gitlab-org/gitlab/-/blob/c03c1be71de6f26f19862ee203084717dbf4c792/doc/user/project/issues/related_issues.md#add-a-linked-issue explains. I suggest that you move there. |
Beta Was this translation helpful? Give feedback.
-
It is often case when one issue blocks another. It will be great to have ability to explicitly set this relation.
Right now in the sidebar there is
Linked Pull Requests. There can be additionalRelated issues, and you could mark any issue in this list as blocked by current issue or as a blocking for current issue.Beta Was this translation helpful? Give feedback.
All reactions