- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
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 experienceto turn it off for now.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.
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.
