Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-1529

Allow removing of sub-tasks in hierarchy and adding of lower levels

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • 0
    • 7
    • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      This hierarchy below is an example of a higher level being added to the default hierarchy:

      I would like to be able to add a level below stories and remove sub-tasks. The reason for this is that stories can be used to represent requirements, but may or may not be able to be completed in a sprint. I would like to test these requirements via manual and automated testing at some point when they are finished, and complete tasks in sprints.

      JIRA doesn't deal we well with having items span multiple sprints, so I would like the tasks to be the work items completed sprint to sprint. This use case assumes a story isn't a product increment that can be finished in a sprint, but a goal or deliverable that will be worked through over time. For example, a slow infrastructure build, that isn't following agile manifesto, but is benefiting from some agile features.

              Unassigned Unassigned
              3833c60e4a12 scarfeb
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal (Inactive)

                Created:
                Updated:
                Archived: