• 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

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3067244 ] New: JAC Suggestion Workflow 3 [ 3658066 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2620697 ] New: JAC Suggestion Workflow [ 3067244 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2318201 ] New: Confluence Workflow - Public Facing v4 [ 2620697 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2038890 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2318201 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2027339 ] New: JIRA PM Feature Request Workflow v2 [ 2038890 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736403 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2027339 ]
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 534574 ] New: JIRA PM Feature Request Workflow v2 [ 736403 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Michael Tokar made changes -
            Link New: This issue duplicates GHS-9455 [ GHS-9455 ]

            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

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

                Created:
                Updated:
                Resolved: