Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-8755

Integrate Structure and Sprint Planning

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

      In GHS-3922, Tom Kotecki writes:

      "Please note that we have already implemented epic support..."

      Epic support is not working well for me, nor are flat backlogs.

      When we do the initial work breakdown structure (WBS) for a project, we enter all the items in a Structure with lots of hierarchy (using Epics and Stories: Epic -> Epic -> Epic -> ... -> Story). We use Epics for the hierarchy, and Stories are only used at the bottom. After we have our WBS, we do the sprint planning. To do the sprint planning based on the WBS, I need the Structure to be integrated with GreenHopper. Today, there is a mini Structure window in the right hand-side panel, and it shows the hierarchical Structure path to the issue highlighted on the rapid board. Instead of this, I need to see the entire Structure on one side of the screen (left), and the rapid board in planning mode on the other side (right). I want to be able to drag items from the Structure and drop them in a sprint on the rapid board in sprint planning mode.

      Next, I will need the issues in the Structure to be visually annotated with the Sprint number they have been dragged into. This way, when I look at the Structure, I will know which issues have been planned and which have not been planned yet.

      Other issues that might be related to this request:
      GHS-2136
      GHS-3922
      GHS-5356
      GHS-5667
      GHS-7690
      GHS-8044
      JRA-29180

              Unassigned Unassigned
              7f28fca79fc9 martinda14
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: