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

Linking & syncing - automated sync of updates from linked issue, e.g. when issue is cloned

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.

      Suggested improvements

      • It is a common case that a service desk ticket is linked to another JIRA Issue (bug) where the customer has no access. In such situation, updates on the bug cannot be seen by customers and it requires manual work from service desk agent to copy updates from the linked JIRA Issue (bug) to the customer facing service desk ticket. At the moment, it is only possible to make an automation of Update when a linked issue changes. The automation can transition the service desk ticket to a certain status but not sync any updates. Allow an automation of syncing updates from the linked issue to the service desk ticket. A rule to check which updates from the linked issue is meant for customer communication would also help.
      • New Automation trigger for "When issue is cloned" - This is similar to JIRAAUTOSERVER-16. The user wants to create an automation that applies an issue link automatically when the issue is cloned (apply to the clone and the cloned issue). Sp far, there is no trigger using "clone" as option. 

      Current workaround for the Clone trigger not being available

      The clone operation is considered a flow of the issue creation operation too. In such case you can use the issue created trigger to listen to clone operations.

      Normally when you clone an issue Jira will automatically link the cloned issue using the link type Cloners. In that case we can use it as a condition to trigger the rule in the right occasions.

      Example:

      • I created an Automation rule as the following
        • Trigger: Issue created
        • Action: Re-fetch issue date
        • Condition: smart valus condition - compare two values
          • I check if {{issue.issuelinks.type}} equals Cloners
        • Action: Comment on issue

        1. Screen Shot 2021-08-27 at 15.13.30.png
          Screen Shot 2021-08-27 at 15.13.30.png
          1.37 MB
        2. Screenshot 2024-09-10 at 11.39.51 AM.png
          Screenshot 2024-09-10 at 11.39.51 AM.png
          321 kB

            [AUTO-564] Linking & syncing - automated sync of updates from linked issue, e.g. when issue is cloned

            Makarand Gomashe made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 999974 ]
            SET Analytics Bot made changes -
            UIS Original: 26 New: 0
            Makarand Gomashe made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 969163 ]
            Makarand Gomashe made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 967508 ]
            Charlie Gavey made changes -
            Link New: This issue is duplicated by AUTO-1525 [ AUTO-1525 ]
            Makarand Gomashe made changes -
            Status Original: Future Consideration [ 11775 ] New: Gathering Interest [ 11772 ]
            Makarand Gomashe made changes -
            Assignee Original: Scott Bell [ dfc44bd03767 ] New: Makarand Gomashe [ 36bd3fea80e3 ]
            Leonardo De Almeida made changes -
            Description Original: h3. Suggested improvements
             * It is a common case that a service desk ticket is linked to another JIRA Issue (bug) where the customer has no access. In such situation, updates on the bug cannot be seen by customers and it requires manual work from service desk agent to copy updates from the linked JIRA Issue (bug) to the customer facing service desk ticket. At the moment, it is only possible to make an automation of {*}Update when a linked issue changes{*}. The automation can transition the service desk ticket to a certain status but not sync any updates. Allow an automation of syncing updates from the linked issue to the service desk ticket. A rule to check which updates from the linked issue is meant for customer communication would also help.
             * New Automation trigger for "When issue is cloned" - This is similar to JIRAAUTOSERVER-16. The user wants to create an automation that applies an issue link automatically when the issue is cloned (apply to the clone and the cloned issue). Sp far, there is no trigger using "clone" as option. 

            h3. Current workaround for the Clone trigger not being available

            The clone operation is considered a flow of the issue creation operation too. In such case you can use the issue created trigger to listen to clone operations.

            Normally when you clone an issue Jira will automatically link the cloned issue using the link type Cloners. In that case we can use it as a condition to trigger the rule in the right occasions.

            Example:
            * I created an Automation rule as the following
            ** Trigger: *Issue created*
            ** Action: *Re-fetch issue date*
            ** Condition: *smart valus condition - compare two values*
            *** I check if *{{{{issue.issuelinks.type}}}}* equals *Cloners*
            ** Action: *Comment on issue*
            		New: h3. Suggested improvements
             * It is a common case that a service desk ticket is linked to another JIRA Issue (bug) where the customer has no access. In such situation, updates on the bug cannot be seen by customers and it requires manual work from service desk agent to copy updates from the linked JIRA Issue (bug) to the customer facing service desk ticket. At the moment, it is only possible to make an automation of {*}Update when a linked issue changes{*}. The automation can transition the service desk ticket to a certain status but not sync any updates. Allow an automation of syncing updates from the linked issue to the service desk ticket. A rule to check which updates from the linked issue is meant for customer communication would also help.
             * New Automation trigger for "When issue is cloned" - This is similar to JIRAAUTOSERVER-16. The user wants to create an automation that applies an issue link automatically when the issue is cloned (apply to the clone and the cloned issue). Sp far, there is no trigger using "clone" as option. 

            h3. Current workaround for the Clone trigger not being available

            The clone operation is considered a flow of the issue creation operation too. In such case you can use the issue created trigger to listen to clone operations.

            Normally when you clone an issue Jira will automatically link the cloned issue using the link type Cloners. In that case we can use it as a condition to trigger the rule in the right occasions.

            Example:
            * I created an Automation rule as the following
            ** Trigger: *Issue created*
            ** Action: *Re-fetch issue date*
            ** Condition: *smart valus condition - compare two values*
            *** I check if *{{{{issue.issuelinks.type}}}}* equals *Cloners*
            ** Action: *Comment on issue*
             !Screenshot 2024-09-10 at 11.39.51 AM.png|thumbnail!
            Leonardo De Almeida made changes -
            Attachment New: Screenshot 2024-09-10 at 11.39.51 AM.png [ 462956 ]
            Leonardo De Almeida made changes -
            Description Original: h3. Suggested improvements
             * It is a common case that a service desk ticket is linked to another JIRA Issue (bug) where the customer has no access. In such situation, updates on the bug cannot be seen by customers and it requires manual work from service desk agent to copy updates from the linked JIRA Issue (bug) to the customer facing service desk ticket. At the moment, it is only possible to make an automation of {*}Update when a linked issue changes{*}. The automation can transition the service desk ticket to a certain status but not sync any updates. Allow an automation of syncing updates from the linked issue to the service desk ticket. A rule to check which updates from the linked issue is meant for customer communication would also help.
             * New Automation trigger for "When issue is cloned" - This is similar to JIRAAUTOSERVER-16. The user wants to create an automation that applies an issue link automatically when the issue is cloned (apply to the clone and the cloned issue). Sp far, there is no trigger using "clone" as option.              		New: h3. Suggested improvements
             * It is a common case that a service desk ticket is linked to another JIRA Issue (bug) where the customer has no access. In such situation, updates on the bug cannot be seen by customers and it requires manual work from service desk agent to copy updates from the linked JIRA Issue (bug) to the customer facing service desk ticket. At the moment, it is only possible to make an automation of {*}Update when a linked issue changes{*}. The automation can transition the service desk ticket to a certain status but not sync any updates. Allow an automation of syncing updates from the linked issue to the service desk ticket. A rule to check which updates from the linked issue is meant for customer communication would also help.
             * New Automation trigger for "When issue is cloned" - This is similar to JIRAAUTOSERVER-16. The user wants to create an automation that applies an issue link automatically when the issue is cloned (apply to the clone and the cloned issue). Sp far, there is no trigger using "clone" as option. 

            h3. Current workaround for the Clone trigger not being available

            The clone operation is considered a flow of the issue creation operation too. In such case you can use the issue created trigger to listen to clone operations.

            Normally when you clone an issue Jira will automatically link the cloned issue using the link type Cloners. In that case we can use it as a condition to trigger the rule in the right occasions.

            Example:
            * I created an Automation rule as the following
            ** Trigger: *Issue created*
            ** Action: *Re-fetch issue date*
            ** Condition: *smart valus condition - compare two values*
            *** I check if *{{{{issue.issuelinks.type}}}}* equals *Cloners*
            ** Action: *Comment on issue*

              36bd3fea80e3 Makarand Gomashe
              rmacalinao Ramon M
              Votes:
              159 Vote for this issue
              Watchers:
              77 Start watching this issue

                Created:
                Updated: