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

Ability to copy values from other fields when using Automation to create an issue

XMLWordPrintable

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

      Currently, it is possible to copy values from certain fields (e.g., Summary and Description), but it would be nice if other fields (including custom fields) could be duplicated when using Automation to create issues.

      • Using fieldChange to populate Labels during issue creation will fail - Currently, if you try to populate the field Labels with a value from a select list field by using the fieldChange smart value it will fail with an error stating that the value contains a space
      • At the moment when you want to use automation Create Service Request you are unable to copy Reporter/Raise this request on behalf of field like you can do with Approver, Summary or Description (just a few examples). - This is already available in Create/Clone Jira Issue

       

            [AUTO-315] Ability to copy values from other fields when using Automation to create an issue

            Charlie Gavey made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Charlie Gavey made changes -
            Link New: This issue duplicates AUTO-328 [ AUTO-328 ]
            Anusha Rutnam made changes -
            Link New: This issue relates to AUTO-328 [ AUTO-328 ]
            Samir made changes -
            Component/s Original: Automation - A4J [ 65590 ]
            Component/s Original: Automation [ 46695 ]
            Component/s New: Condition - Issue Fields [ 70305 ]
            Component/s New: Action - Issue Actions [ 71497 ]
            Key Original: JSDCLOUD-8929 New: AUTO-315
            Project Original: Jira Service Management Cloud [ 18512 ] New: Automation for Cloud [ 22610 ]
            Charlie Gavey made changes -
            Component/s New: Automation - A4J [ 65590 ]
            Charlie Gavey made changes -
            Link New: This issue is duplicated by JSWCLOUD-23093 [ JSWCLOUD-23093 ]
            Charlie Gavey made changes -
            Link New: This issue is duplicated by JSDCLOUD-10385 [ JSDCLOUD-10385 ]
            Charlie Gavey made changes -
            Description Original: Currently, it is possible to copy values from certain fields (e.g., *Summary* and {*}Description{*}), but it would be nice if other fields (including custom fields) could be duplicated when using *Automation* to create issues.
             * Using \{{fieldChange}} to populate Labels during issue creation will fail - Currently, if you try to populate the field *Labels* with a value from a select list field by using the *{{fieldChange}}* smart value it will fail with an error stating that the value contains a space:             		New: Currently, it is possible to copy values from certain fields (e.g., *Summary* and {*}Description{*}), but it would be nice if other fields (including custom fields) could be duplicated when using *Automation* to create issues.
             * Using {{fieldChange}} to populate Labels during issue creation will fail - Currently, if you try to populate the field *Labels* with a value from a select list field by using the *{{fieldChange}}* smart value it will fail with an error stating that the value contains a space
             * At the moment when you want to use automation *Create Service Request* you are unable to copy *Reporter/Raise this request on behalf of* field like you can do with *Approver, Summary or Description* (just a few examples). - This is already available in Create/Clone Jira Issue

             
            Charlie Gavey made changes -
            Description Original: Currently, it is possible to copy values from certain fields (e.g., *Summary* and *Description*), but it would be nice if other fields (including custom fields) could be duplicated when using *Automation* to create issues. New: Currently, it is possible to copy values from certain fields (e.g., *Summary* and {*}Description{*}), but it would be nice if other fields (including custom fields) could be duplicated when using *Automation* to create issues.
             * Using \{{fieldChange}} to populate Labels during issue creation will fail - Currently, if you try to populate the field *Labels* with a value from a select list field by using the *{{fieldChange}}* smart value it will fail with an error stating that the value contains a space:
            Charlie Gavey made changes -
            Link New: This issue is duplicated by JSDCLOUD-9087 [ JSDCLOUD-9087 ]

              Unassigned Unassigned
              mmarney@atlassian.com Matthew M. (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: