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

      Advanced Roadmaps (former Portfolio) extends issue hierarchies and uses the concept of Parent Link, which has a custom field associated with it.
      We should include support for this in Automation for Jira, such as the examples:

      • Branches to Parent/Child.
      • Setting/editing field actions.
        • Including Copy value from.
      • Smart Values to access field values from related issues on the hierarchy.

      This is a similar request to - https://codebarrel.atlassian.net/browse/AUT-1779

            [JIRAAUTOSERVER-135] Support "Parent Link" fields

            Would be nice to have this functionality built-in so its more of a "point and click" operation vs custom coding. Would help less experienced users. 

            Aaron Matthys added a comment - Would be nice to have this functionality built-in so its more of a "point and click" operation vs custom coding. Would help less experienced users. 

            This is really needed! And it works in the cloud.

            We need to be able to trigger an automation when the parent link is changed - and I can't find any other way to this, without the parent link being supported in automation.

            Claus Østergaard Pedersen added a comment - This is really needed! And it works in the cloud. We need to be able to trigger an automation when the parent link is changed - and I can't find any other way to this, without the parent link being supported in automation.

            Thanks @Lara Lopez that definitely works.

            Brad Fitpatrick added a comment - Thanks @Lara Lopez that definitely works.

            The workaround with smartvalues is:

            Replace the customfield id with the ID of your Parent Link customfield and set the issue you prefer.

            {
                "update" : {
                    "customfield_15005" : [{"set" : "{{triggerIssue}}"}]
                }
            } 

            Lara Lopez added a comment - The workaround with smartvalues is: Replace the customfield id with the ID of your Parent Link customfield and set the issue you prefer. {     "update" : {         "customfield_15005" : [{ "set" : "{{triggerIssue}}" }]     } }

            Hello everyone, 

            I don't know if this solution is applicable to all your cases, but I've made this KB describing a method to copy values from any "direction" without branching blocks, please give it a look:

            How to copy custom field values to the trigger issue using the Parent Link field (without using branch blocks)

            I would appreciate any feedback!

            Kind regards,

            Pietro Lemes
            Atlassian Support

            Pietro Lemes added a comment - Hello everyone,  I don't know if this solution is applicable to all your cases, but I've made this KB describing a method to copy values from any "direction" without branching blocks, please give it a look: How to copy custom field values to the trigger issue using the Parent Link field (without using branch blocks) I would appreciate any feedback! Kind regards, Pietro Lemes Atlassian Support

            This is such a HUGE use case for all scaled agile implementation that wants to build a sensible work breakdown structure and it's very painful that we have to create manual scripted workarounds for this.

            Daniel Zinsli added a comment - This is such a HUGE use case for all scaled agile implementation that wants to build a sensible work breakdown structure and it's very painful that we have to create manual scripted workarounds for this.

            rknu added a comment -

            I have been using a solution described here to make Epic status change my Jira Roadmap parent issue (like Initiatives).

            Primarily it is the branched JQL:  

            issue in parentIssuesOf("{{issue.key}}") 

            that helped with transition of parent issue based upon the Epic status.

             

            However I have not been able to find a way to validate that all Epics has been completed ("Done") before transition of parent issue ("Initiative").

            It would be nice if there was a simple why to do this like with Epic and issues in the Epic.

             

            rknu added a comment - I have been using a solution described here to make Epic status change my Jira Roadmap parent issue (like Initiatives). Primarily it is the branched JQL:   issue in parentIssuesOf( "{{issue.key}}" ) that helped with transition of parent issue based upon the Epic status.   However I have not been able to find a way to validate that all Epics has been completed ("Done") before transition of parent issue ("Initiative"). It would be nice if there was a simple why to do this like with Epic and issues in the Epic.  

            Anyone know a workable workaround for this? Very hard to create grouped Roadmaps without lots of manual admin on my end. 

            Adam Parrish added a comment - Anyone know a workable workaround for this? Very hard to create grouped Roadmaps without lots of manual admin on my end. 

            Cannot edit Initiative issue field over "Advanced roadmap" Parent link/Child issues relation type. Need to gather values from child Epics and sum under Initiative: idea would be use something like issue.childIssue.CustomFieldName.sum

            I guess this is not possible and this development could fix my issue?!

            Ragnar Veermäe added a comment - Cannot edit Initiative issue field over "Advanced roadmap" Parent link/Child issues relation type. Need to gather values from child Epics and sum under Initiative: idea would be use something like issue.childIssue.CustomFieldName.sum I guess this is not possible and this development could fix my issue?!

              Unassigned Unassigned
              abrancalhao@atlassian.com Armando Neto
              Votes:
              146 Vote for this issue
              Watchers:
              74 Start watching this issue

                Created:
                Updated: