GitHub

127 readers

4 users here now

A community for discussion and posts relating to github https://github.com/

founded 1 year ago

MODERATORS

pylapp

Evolving GitHub Issues (public preview) (github.blog)

submitted 1 day ago by [email protected] to c/github

3 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] popcar2 5 points 1 day ago* (last edited 1 day ago) (2 children)

I saw this in my repos and still don't understand why subissues exist. I feel like this overcomplicates things, a checklist inside of an issue has the same effect. If you're going to assign sub-issues to different people, shouldn't they be just separate issues?

Anyways you can click on your profile in the top right --> feature previews --> disable new issue experience to turn it off for now.

[–] secana 6 points 1 day ago

I've the same feeling about sub-issues. I don't want the corporate pain of Jira to be replicated in Github. If you can't structure one issue to be comprehensive, multiple sub-issues won't help you either.

[–] FizzyOrange 3 points 1 day ago

Sometimes a big task is made up of smaller components that you can complete on their own, and you want to keep track of things. They definitely have a use.

However the way Jira does subtasks is quite dumb, e.g. you can only have a single level. I hope they haven't copied that blindly. I much prefer Phabricator where you can just give any task a parent. They can even have multiple parents.