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

Issue Linking with Custom Hierarchy in Live Plans

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Integration
    • None
    • 35
    • 5

    • 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.

      Issue linking should persist and be visible when a custom hierarchy is in use.

      As an example:

      • Feature
      ---- Epic
      ---- Story

      Epic Link is used to create the relationship between the Story and Epic. We use "Issue Link" "parent" to establish the link/hierarchy between the Feature and Epic. On import in the Portfolio Live Plan, and after adding the Feature issue type to the hierarchy in Portfolio, the Epic/Story link is honored while the Feature/Epic link is not.

      At this point we manually linked all the Features/Epics in Portfolio, and committed the changes. There is no visible relationship added on the single JIRA issues outside of Portfolio.

      Ideally the linking is imported along with the issues, and is also updated/maintained when changed within Portfolio.

              Unassigned Unassigned
              ab47eac11abb Shaun Collins
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: