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

Ability to create Epic buckets for overall features that contain Epics, Stories and Sub-tasks

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Timed out
    • 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.

      Problem Definition

      Would like to be able to group all of my Epics for a certain feature together into one bucket

      Suggested Solution

      For example:

      Overall Feature: Feature 1
      20 Epics, where each Epic has 20 - 30 User Stories, and each User Story has 5 - 10 subtasks.

      Overall Feature: Feature 2
      15 Epics, where each Epic has 10 User Stories, and each User Story has 5 - 8 subtasks.

      Overall Feature: Feature 3

      17 Epics, where each Epic has 12 User Stories, and each User Story has 8 - 12 subtasks.

      In this case, Epic, Story, and Story Subtask are all existing JIRA issues. End user would like to create a bucket of a JIRA issue containing all of the overall Epics: Feature 1, Feature 2 and Feature 3

      Workaround

      Third-party add-on that add this functionality to JIRA here: https://marketplace.atlassian.com/plugins/com.almworks.jira.structure/server/overview. Unfortunately, it is only available for JIRA Server.

      End user could as separate Feature 1, Feature 2 and Feature 3 their own separate projects. Then create a saved JQL filter to search for all Epics in project. Setup a JQL filter to search for all Epics in project Feature 1. Will not update systematically as JQL filter will need to be changed everything new Epic is added to Feature 1.

      Another possible workaround would be for the end user to create a multi-project agile board governed by epic swimlanes. Create board title Feature 1 and manually configure the board filter to contains all 20 Epics in Feature 1. Will not automatically update when you create additional Epics for Feature 1 as the JQL board configuration will need to be adjusted

              Unassigned Unassigned
              jromero@atlassian.com Jose R. (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: