• 3
    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      so that I can save time in grooming and I can see all information for what I am splitting.

      Example Scenarios:

      • I created an epic that is too large. I want to split it into 2 and re-define requirements across two epics.
      • In grooming, one story is estimated too large. I want to split it into two stories

      Current Solution:
      Cloning - However, I lose track when using two tabs. I would do it away from the team and they have to wait on a future grooming to re-estimate.

            [JSWCLOUD-9929] As a Product Owner I want to split an epic easily

            Thomas added a comment -

            Any chance of this actually getting done? It's been around for years, and so far there's only the split in the backlog view - which is not applicable for epics.

            Thomas added a comment - Any chance of this actually getting done? It's been around for years, and so far there's only the split in the backlog view - which is not applicable for epics.

            I really like Option 2, that would work well for us.

            Martin Gill added a comment - I really like Option 2, that would work well for us.

            In case it would help, I asked a few questions and I think this would be more or less what we would like:

            OPTION 1: This would be nice.
            =======================
            1. Right button on a story -> Split
            2. On a popup, I see all subtasks, each with a checkbox on its left.
            3. I check the ones I want to go to the new story
            4. I click OK, and get a new story called the same as the first one, but with "2" added at the end, which contains the subtasks I selected.

            If I would do that again, I would get another story, this time with a "3" at the end.

            OPTION 2: This is what we really would like!
            =================================
            1. Right button on a story -> Split
            2. On a popup, I see two columns (one for the current story and other for the new one)
            3. I can drag and drop subtasks from the first story to the other one.
            4. Clicking a button I can create another column, so I can split the story in more than two substories (we do this a lot).

            Hope it helps!

            Fernando Claros added a comment - In case it would help, I asked a few questions and I think this would be more or less what we would like: OPTION 1: This would be nice. ======================= 1. Right button on a story -> Split 2. On a popup, I see all subtasks, each with a checkbox on its left. 3. I check the ones I want to go to the new story 4. I click OK, and get a new story called the same as the first one, but with "2" added at the end, which contains the subtasks I selected. If I would do that again, I would get another story, this time with a "3" at the end. OPTION 2: This is what we really would like! ================================= 1. Right button on a story -> Split 2. On a popup, I see two columns (one for the current story and other for the new one) 3. I can drag and drop subtasks from the first story to the other one. 4. Clicking a button I can create another column, so I can split the story in more than two substories (we do this a lot). Hope it helps!

            This is quite a problem for us too, mainly because is something strictly related to the UI, so people is less tolerant to it (they see the need to split stories, but since the software doesn't make it easy for them to do so, they become irritated and stories don't end up being properly split).

            Fernando Claros added a comment - This is quite a problem for us too, mainly because is something strictly related to the UI, so people is less tolerant to it (they see the need to split stories, but since the software doesn't make it easy for them to do so, they become irritated and stories don't end up being properly split).

              Unassigned Unassigned
              c252a387a3b2 Gino Toro
              Votes:
              23 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: