Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-377

A4J: Support for JIRA Portfolio hierarchy and "Parent Link" fields, e.g. update Field Value Changed trigger to support an issue's parent changing to trigger an action

XMLWordPrintable

    • 87

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

      Portfolio uses the concept of Parent Link and has a customfield.
      We Should support this in Automation for Jira:

      • Field value changed trigger - Automation Field Value Change Trigger should work with Parent or Epic Link changes - The Automation Field Value Change Trigger does not allow you to select the Epic Link field to trigger actions based on an issue's Epic Link changing. It also does not allow you to select an issue's parent changing to trigger an action.
      • Setting/editing on field actions
      • Branch traversal
      • smart-values
        We are however searching for a method to (automatically) copy comments from high level issue types/Initiatives to 'lower' levels, or to set specific fields based on a issue transition on a higher level.

              Unassigned Unassigned
              hnyeche Prince N
              Votes:
              196 Vote for this issue
              Watchers:
              119 Start watching this issue

                Created:
                Updated: