Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-71

Add support for nested branches (a branch within another branch)

XMLWordPrintable

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

      It would be great if we could branch within branches.

      For example, 'transition subtask based on another subtask transitioning'

      This use case would be solved much easier with this feature.

            [JIRAAUTOSERVER-71] Add support for nested branches (a branch within another branch)

            Marc Dacanay made changes -
            Labels Original: iq-a4j New: iq-a4j ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 978955 ]
            Mateo made changes -
            Link Original: This issue was cloned as AUTO-89 [ AUTO-89 ]
            Mateo made changes -
            Link New: This issue relates to AUTO-67 [ AUTO-67 ]

            NBENTO added a comment -

            +1

            NBENTO added a comment - +1

            Mauricio Heberle added a comment -

            +1

            Mauricio Heberle added a comment - +1
            Michelle Chin made changes -
            UIS New: 0
            Rudy Slaiby made changes -
            Labels New: iq-a4j

            tjwood added a comment -

            Need this to trigger creation of chain of subsequent issues so that I can trigger the status change of each issue according to the status of it's trigger issue by automatically setting up Related Link of "Caused By" between each issue and the issue it triggers (during issue creation), then by setting condition and trigger to change the status of subsequent issue when the status of the issue that triggered it (now marked as Linked "caused by" issue) is changed to done. (All of this of course happening along with each issue's own status automatically being set to done when the status of all sub-tasks I automatically triggered for each issue are set manually to done.)

             

            Alternatively, need a condition that allows setting of status on a field based of status of any other specific field I select in the entire automation rule. That would be easier, but I'd take the more complicated option too since nesting branches will have other uses too.

            tjwood added a comment - Need this to trigger creation of chain of subsequent issues so that I can trigger the status change of each issue according to the status of it's trigger issue by automatically setting up Related Link of "Caused By" between each issue and the issue it triggers (during issue creation), then by setting condition and trigger to change the status of subsequent issue when the status of the issue that triggered it (now marked as Linked "caused by" issue) is changed to done. (All of this of course happening along with each issue's own status automatically being set to done when the status of all sub-tasks I automatically triggered for each issue are set manually to done.)   Alternatively, need a condition that allows setting of status on a field based of status of any other specific field I select in the entire automation rule. That would be easier, but I'd take the more complicated option too since nesting branches will have other uses too.
            Ratnarup made changes -
            Link New: This issue was cloned as JIRAAUTOSERVER-472 [ JIRAAUTOSERVER-472 ]

              Unassigned Unassigned
              jrey Julien Rey
              Votes:
              79 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated: