Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-64218

Identify issues based on their Epic's Parent Link or other attribute (sub-queries ideally)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      This for JIRA Cloud

      We use JIRA Portfolio's Parent Link field to link JIRA epics (SAFe Features) up to SAFe Epics (custom issue type). 

      I need to be able to identify all issues based on their grandparent, and ideally on any other attribute of the JIRA Epic they belong to.

      Either live in JQL as sub-queries, or some mechanism to (regularly or on request) to find them and label them so they can be found via that label search.

      For example, I want to be able to have a board that showed all issues that were part of any epic whose Parent Link was a specific issue (SAFe Epic)... something like:

      {{ "Epic Link" in ("Parent Link" = ABC-53)}}

      This of course fails.

      I've tried in Cloud using post-function based approaches (standard and JMWE), and have explored most of the add-ons available in cloud, but can't figure out how to do this.

       

      This is fundamental in our SAFe adoption so we can show all the work supporting a particular SAFe Epic (which may be split across multiple Features in several release trains / programs, and across multiple teams). 

       

      Please advise when some workaround of capability will be available in Cloud, or if this can be achieved through a cloud add-on or other approach.

              Unassigned Unassigned
              2e6d87d594eb PTorrSmithMSD
              Votes:
              6 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: