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

    • 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

            +1 for custom fields. 

            Joe Longstreet added a comment - +1 for custom fields. 

            ADMIN added a comment -

            +1
            We are looking to automate the trafficking of tickets through Jira Service Desk's "Automation" feature. It would be awesome to be able to use the 'variables' (specifically ${sourceissue.reporter} ) to store the reporters name in a field on the linked issue. Right now you can only use that variable in 2 fields on the 'create linked issue' screen - summary and description.

             

            ADMIN added a comment - +1 We are looking to automate the trafficking of tickets through Jira Service Desk's "Automation" feature. It would be awesome to be able to use the 'variables' (specifically  ${sourceissue.reporter}  ) to store the reporters name in a field on the linked issue. Right now you can only use that variable in 2 fields on the 'create linked issue' screen - summary and description.  

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

                Created:
                Updated:
                Resolved: