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

Update request type names on Automation rules when modified in Jira

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.

      Description

      Currently, when you rename Request Types on your project, any Automation Rule that have a condition referencing a request type will not be updated and will break.

      It is necessary to manually modify all automations that have Request Types referenced to the new names, and that might take a lot of work depending on how many rules there are in the instance, and how many request type's name were changed.

          Form Name

            [AUTO-310] Update request type names on Automation rules when modified in Jira

            Charlie Gavey made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Charlie Gavey made changes -
            Link New: This issue blocks AUTO-468 [ AUTO-468 ]
            Vipul Reddy made changes -
            Labels Original: automation New: automation jsw-s13

            Szabó Dávid added a comment -

            +1

            Szabó Dávid added a comment - +1
            Samir made changes -
            Component/s Original: Automation - A4J [ 65590 ]
            Component/s New: Condition - Issue Fields [ 70305 ]
            Key Original: JSDCLOUD-10250 New: AUTO-310
            Project Original: Jira Service Management Cloud [ 18512 ] New: Automation for Cloud [ 22610 ]
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            UIS New: 1

            Kevin Bianchi added a comment -

            Hi Altassian,

            Please, fix this problem quickly!

            We have lots of customer that create Jira Automation and add condition on the Request Type field. 

            And when they modify the name, the rule is broken! This is a nightmare to administer it right, because you will for sure forget to modify the automation rule when you modify the name.

            Please change the way Jira automation store the Request Type field by storing the ID. 

             

            For information, the workaround described in this ticket could also help for this topic: https://jira.atlassian.com/browse/JSDCLOUD-11542

            Kevin Bianchi added a comment - Hi Altassian, Please, fix this problem quickly! We have lots of customer that create Jira Automation and add condition on the Request Type field.  And when they modify the name, the rule is broken! This is a nightmare to administer it right, because you will for sure forget to modify the automation rule when you modify the name. Please change the way Jira automation store the Request Type field by storing the ID.    For information, the workaround described in this ticket could also help for this topic:  https://jira.atlassian.com/browse/JSDCLOUD-11542
            Felipe Prusch (Inactive) made changes -
            Labels New: automation
            Felipe Prusch (Inactive) created issue -

              Unassigned Unassigned
              fprusch Felipe Prusch (Inactive)
              Votes:
              26 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: