Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-24832

Parent link should behave in the same way as epic link (i.e. forming a link in the background)



    • 23
    • 16
    • 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 Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      As per all of the comments here: https://answers.atlassian.com/questions/39986944/answers/40347822/comments/43110013

      The key concerns for us with the current implementation are:

      • It's not possible to use ScriptRunner's JQL functions (or indeed functions from a variety of add ons) to find children of initiatives that meet certain criteria. With a normal link, or even epic link, it is possible to run JQL to find all linked issues where the parent issue meets certain criteria - for enterprise this is absolutely critical.
      • It's not possible to update the field via scripts, it's possible to do this for epic links
      • It's not possible to use add ons like Structure to build hierarchies as this isn't a real link type
      • It's not possible to use this field for any kind of reporting outside of JIRA as it doesn't extract the issue key

      This basically means the current implementation of the field/JQL is only useful if you want to find the epics linked to known parent initiatives, which only works if you have a small set of initiatives to work with - we have thousands, and cannot currently create a background link to use for searching when a "parent link" is created because we can't access the field value via scripts.

      Please feel free to contact me if you would like more information about our use cases.


        Issue Links



              Unassigned Unassigned
              ef1b9dd290ec Maree Milne
              211 Vote for this issue
              128 Start watching this issue