Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-9964

Assets Automation: Add support for copying multiple values of Asset data using Automation

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

      While using automation actions we can create an Insight Object and set its attributes. The problem is that when we have an Insight field that accepts multiple objects(see print below) we can't copy those values to an Insight attribute.

      Use case

      User has an onboarding process and whenever ticket reaches a specific status on their workflow they want automation rule to create a new Object on insight. This "User" object type has an attribute on Insight that supports unlimited references to another object type (Systems).

      Something like below is not supported:

      Suggestion

      It would be nice if we could

      • Copy a list of objects to an Insight object attribute that is created via automation.
      • Append Insight attributes to existing values
      • Edit the Insight attributes with more than 1 value
      • Edit the object type Insight attribute with more than 1 value

      Workaround

      Here are two workarounds to try for a few of the features mentioned under the suggestion. 

            [JSDCLOUD-9964] Assets Automation: Add support for copying multiple values of Asset data using Automation

            hi @Thiago Behm

            Thanks for the update and work. Is there now a way to remove the values that we add to an attributes object with this update? Thanks

            Mauricio Heberle added a comment - hi @ Thiago Behm Thanks for the update and work. Is there now a way to remove the values that we add to an attributes object with this update? Thanks

            Hey folks,

            We are glad to see that some of you guys are already taking advantage of this new automation capability.

            Adding to this, I would like to share that our update has addressed the concern brought on by the use case section of this feature. Right below follows an excerpt from the ticket description:

            User has an onboarding process and whenever a ticket reaches a specific status on their workflow they want an automation rule to create a new Object on insight. This "User" object type has an attribute on Insight that supports unlimited references to another object type (Systems).

            Therefore that means that now you can create Assets and assign multiple values to its attribute(as long as it accepts multiple references). For example, we could use something similar to any of the syntax below in order to assign multiple assets:

            {{#triggerIssue.Insight Field (System)}}{{id}}{{/}}
            
            {{triggerIssue.customfield_10068}}
            

            In case you have any questions or face issues, please get in touch with our support team https://support.atlassian.com/contact/.

            Regards,
            Thiago Behm

            Thiago Behm. added a comment - Hey folks, We are glad to see that some of you guys are already taking advantage of this new automation capability. Adding to this, I would like to share that our update has addressed the concern brought on by the use case section of this feature. Right below follows an excerpt from the ticket description: User has an onboarding process and whenever a ticket reaches a specific status on their workflow they want an automation rule to create a new Object on insight. This "User" object type has an attribute on Insight that supports unlimited references to another object type (Systems). Therefore that means that now you can create Assets and assign multiple values to its attribute(as long as it accepts multiple references). For example, we could use something similar to any of the syntax below in order to assign multiple assets: {{#triggerIssue.Insight Field (System)}}{{id}}{{/}} {{triggerIssue.customfield_10068}} In case you have any questions or face issues, please get in touch with our support team https://support.atlassian.com/contact/ . Regards, Thiago Behm

            That did the trick! Thanks!!!

            maurício heberle added a comment - That did the trick! Thanks!!!

            @Mauricio Heberle I am storing all the Keys of Insight Object into a variable which were selected in the Insight Custom Field. Then I am using FOR IQL (with IN clause) in Automation and making the edits.

             Example for Query : Key In (assetkeys)

            Mahender Kumar added a comment - @Mauricio Heberle I am storing all the Keys of Insight Object into a variable which were selected in the Insight Custom Field. Then I am using FOR IQL ( with IN clause ) in Automation and making the edits.  Example for Query : Key In ( assetkeys )

            @Mahender Kumar I tried to edit an attribute with cardinality in automation, but no success. How did you do?

            Mauricio Heberle added a comment - @Mahender Kumar I tried to edit an attribute with cardinality in automation, but no success. How did you do?

            Yes, it is in prod  thanks Manuela for your comment that I was able to revisit and found it implemented

            Mahender Kumar added a comment - Yes, it is in prod  thanks Manuela for your comment that I was able to revisit and found it implemented

            Great news! Is this is in prod already?

            Mauricio Heberle added a comment - Great news! Is this is in prod already?

            Manuela added a comment -

            Waiting for implementation!

            Manuela added a comment - Waiting for implementation!

            Extremely important feature, needs to be solved

            Mauricio Heberle added a comment - Extremely important feature, needs to be solved

            The workarounds described are located in the Jira 9 DC documentation, as where it should be in the Cloud section.

            Patrick van der Rijst added a comment - The workarounds described are located in the Jira 9 DC documentation, as where it should be in the Cloud section.

              msingh3@atlassian.com Mandeep Singh
              tbehm@atlassian.com Thiago Behm.
              Votes:
              86 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated:
                Resolved: