Subtasks for issues (BB-7249)

Issue #6043 wontfix
andersra88 created an issue

Can we PLEASE have subtasks. This would work similar to JIRA tasks, allowing hierarchical relationships between issues.

Comments (39)

  1. Jonathan Mooring
    • changed status to open

    Thank you for your feedback. We don't currently have any near-term plans to add sub-tasks to the issue tracker, but I'll be leaving this issue open for additional feedback from the community.


  2. Dylan Etkin

    We have decided to keep our issue tracker very simple.

    If you require subtasks then I suggest you use a more complex issue tracker such as JIRA.



  3. Espen Ellingsen

    Subtasks are essential and doesn't really add that much complexity to logics. Please reconsider.

  4. James LaPenn

    Years old issue at this point, but my need for such functionality hasn't changed in a decade. I guess this makes GitHub, GitLab and Gitorious better than BitBucket since you can use this functionality through markdown. I'll have to move my projects over to a paid Github account since BitBucket can't provide such simple and important tools for complex project tracking.

  5. Shahar Dekel

    It makes sense to have sub-tasks integrated in bitbucket. I found the need for it when I wanted to create a task that cannot be completed before a previous task, but have to way to tie the two tasks together. Please reconsider (or is there another solution)?

  6. Gregory

    This would make things a lot cleaner for me. I think the benefit of moving to jira comes in its many other features, not specifically subtasks, so there would still be plenty of draw to upgrading if that's a concern.

  7. Steven Fuqua

    Bitbucket's Issue Tracker is its weakest point for me. I don't think subtasks (or dependencies on other tasks, which would be a workaround) add that much complexity.

    I really need some structured, supported way to break up a large task into multiple pieces.

  8. Philippe Martin

    Subtasks directly in bitbucket could be awesome, Please reconsider it for your entire community.

  9. Gerald Anthony Piangco

    It would really be a great feature for Bitbucket to have this. I vote for a reconsideration as well.

  10. Adrian Z.

    It would be a good idea to reconsider this as the major alternatives (GitHub, Gitlab) have the feature for ages.

  11. guillaume gigonzac

    Note that the feature does not need to be very complex: a simple reference between tasks and subtasks could go a long way, even with no other functionality.

  12. Maximilian Edich

    +1 for subtasks!

    The most simple design for this in my opinion is just one single additional line of text field, where you can enter issue numbers. These will then be visualized as referenced tasks. Nevertheless, real subtasks would be much better. Please, reconcisder your decision.

  13. Collin Klopfenstein's not that they think it's too complicated. They just want us to pay for JIRA instead haha.

    That said... +1 lol

  14. Log in to comment