GitHub introduces sub-issues, issue types and advanced search

Re:GitHub introduces sub-issues, issue types and advanced se... by kkaatii on Thursday January 16, 2025 @09:56AM (#42726038)

The sub-issue structure seems much better than Jira's approach where everything has to fit into a hierarchy. Then it becomes hard to align on the definition of a certain level in the hierarchy.

This create-a-subissue-when-needed way is more sensible.

[ Parent | on HN ]

Re:GitHub introduces sub-issues, issue types and advanced se... by WorldMaker on Thursday January 16, 2025 @11:11AM (#42727205)

It's also not that different from what people have been using Task Lists for today: https://docs.github.com/en/get-started/writing-on-github/wor...

I think that's maybe my biggest question is what the interop looks like between Task Lists and Sub-Issues. Is there a "one-click upgrade" yet? What if I want to copy a list of Sub-Issues as Markdown Task List to copy into a Discussion or a Wiki somewhere?

[ Parent | on HN ]

Re:GitHub introduces sub-issues, issue types and advanced se... by trallnag on Thursday January 16, 2025 @12:38PM (#42728312)

You can use a single type of issue in Jira and just rely on linking them together

[ Parent | on HN ]

Re:GitHub introduces sub-issues, issue types and advanced se... by kkaatii on Thursday January 16, 2025 @09:40PM (#42733532)

Wow i didn't know that.

[ Parent | on HN ]

Re:GitHub introduces sub-issues, issue types and advanced se... by IshKebab on Sunday January 19, 2025 @04:29AM (#42755457)

Yeah we ended up doing this. You should basically never use Epics or Subtasks in Jira because they have weird unnecessary restrictions that don't apply to normal tasks, especially around putting them in sprints.

[ Parent | on HN ]