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

Ability to copy Automation rules and components (actions and conditions)

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

      As a rule writer

      I want to copy and paste (clone) components within a rule

      So I can rapidly create rules which have repeated branches, conditions, and actions

       

      Acceptance criteria:

      • Branch, condition, and action components can be cloned
      • When a component is cloned, it is placed immediately below its source component
      • When a branch is cloned, the child components of the branch are also cloned
      • When a condition is cloned, the child components of the condition are also cloned
      • Bonus: cloning can occur manually by editing a JSON rule file, leaving the component identifiers blank, and then importing the rule for a project.

      Business case:

      The user interface for rule automation allows rapid creation of rules in most ways, except for adding components.  When rules have a repeated pattern, there is no work-around other than to add each component, one by one.  Providing a component clone feature will dramatically speed up the creation of such rules.

       

      ***

      Add an option to copy automation rules between projects - 

      We have 200+ projects mapped to our different clients, one project per client.

      Each of these projects have the same automation rule set that is currently manually applied to them one by one.

      An option to create the rule once and them copy it to another project will be very helpful.

       

            [AUTO-29] Ability to copy Automation rules and components (actions and conditions)

            Michael Fedulov made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Reviewing [ 11773 ] New: Closed [ 6 ]
            Michael Fedulov made changes -
            Assignee Original: Charlie Gavey [ 89403358cf11 ] New: Michael Fedulov [ b5485955f50a ]
            Anusha Rutnam made changes -
            Link Original: This issue duplicates AUTO-360 [ AUTO-360 ]
            Anusha Rutnam made changes -
            Link New: This issue relates to AUTO-360 [ AUTO-360 ]
            Anusha Rutnam made changes -
            Link New: This issue duplicates AUTO-360 [ AUTO-360 ]
            Charlie Gavey made changes -
            Status Original: Gathering Interest [ 11772 ] New: Reviewing [ 11773 ]
            Charlie Gavey made changes -
            Description Original: As a rule writer

            I want to copy and paste (clone) components within a rule

            So I can rapidly create rules which have repeated branches, conditions, and actions

             

            Acceptance criteria:
             * Branch, condition, and action components can be cloned
             * When a component is cloned, it is placed immediately below its source component
             * When a branch is cloned, the child components of the branch are also cloned
             * When a condition is cloned, the child components of the condition are also cloned
             * Bonus: cloning can occur manually by editing a JSON rule file, leaving the component identifiers blank, and then importing the rule for a project.

            Business case:

            The user interface for rule automation allows rapid creation of rules in most ways, except for adding components.  When rules have a repeated pattern, there is no work-around other than to add each component, one by one.  Providing a component clone feature will dramatically speed up the creation of such rules.

            .

             
            New: As a rule writer

            I want to copy and paste (clone) components within a rule

            So I can rapidly create rules which have repeated branches, conditions, and actions

             

            Acceptance criteria:
             * Branch, condition, and action components can be cloned
             * When a component is cloned, it is placed immediately below its source component
             * When a branch is cloned, the child components of the branch are also cloned
             * When a condition is cloned, the child components of the condition are also cloned
             * Bonus: cloning can occur manually by editing a JSON rule file, leaving the component identifiers blank, and then importing the rule for a project.

            Business case:

            The user interface for rule automation allows rapid creation of rules in most ways, except for adding components.  When rules have a repeated pattern, there is no work-around other than to add each component, one by one.  Providing a component clone feature will dramatically speed up the creation of such rules.

             

            ***

            Add an option to copy automation rules between projects - 

            We have 200+ projects mapped to our different clients, one project per client.

            Each of these projects have the same automation rule set that is currently manually applied to them one by one.

            An option to create the rule once and them copy it to another project will be very helpful.

             
            Charlie Gavey made changes -
            Link New: This issue is duplicated by AUTO-195 [ AUTO-195 ]
            Charlie Gavey made changes -
            Link New: This issue is duplicated by AUTO-73 [ AUTO-73 ]
            Charlie Gavey made changes -
            Component/s Original: Automation [ 68402 ]
            Component/s New: Rule - Edit Components [ 70298 ]
            Key Original: JSWCLOUD-22765 New: AUTO-29
            Workflow Original: JAC Suggestion Workflow JSWCLOUD [ 4267021 ] New: JAC Suggestion Workflow 3 [ 4297782 ]
            Project Original: Jira Software Cloud [ 18511 ] New: Automation [ 22610 ]

              b5485955f50a Michael Fedulov
              c48be19ba6fe William Sheboy
              Votes:
              71 Vote for this issue
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: