• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Customers would like the ability to separate subtasks from parents when viewing them in work mode on a rapidboard. This is in order to track/assign work to different users via subtasks while still under a single parent task.

            [JSWSERVER-9077] Add the ability to separate subtasks from parents

            I'm resolving this issue as a duplicate of the linked issue, since what I believe you are asking for is a way to have Stories at the same level as Epics, so that Sub-tasks will come up to the same level as Stories.

            In your particular use case, have you considered using the existing Epics feature that we have today? That way you could split your features (captured by Epics) into Stories, which each have their own technical sub-tasks.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - I'm resolving this issue as a duplicate of the linked issue, since what I believe you are asking for is a way to have Stories at the same level as Epics, so that Sub-tasks will come up to the same level as Stories. In your particular use case, have you considered using the existing Epics feature that we have today? That way you could split your features (captured by Epics) into Stories, which each have their own technical sub-tasks. Regards, JIRA Agile Team

            kate added a comment -

            Thank you for capturing this, Turner. The business case is that the product team will create the stories for the new features and products, but they have a higher level of detail. The engineering team would like a hierarchical way to link to that story while having their own separate issues that detail exactly what needs to be done on a technical level.

            For example, when frontend development and backend development need to be done for the same feature, and different team members are performing each piece of work.

            kate added a comment - Thank you for capturing this, Turner. The business case is that the product team will create the stories for the new features and products, but they have a higher level of detail. The engineering team would like a hierarchical way to link to that story while having their own separate issues that detail exactly what needs to be done on a technical level. For example, when frontend development and backend development need to be done for the same feature, and different team members are performing each piece of work.

              Unassigned Unassigned
              cbenard Carlen Benard (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: