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

@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?

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?

Waiting for implementation!

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.

+1 this is much needed

@swati thanks for your workaround. I tried this for my self but got an array error "was expecting comma to separate Object entries\n"

Tried to catch the variable to see what it is and it looks comma separated...

"BU-9232,BU-9240,BU-9243,BU-9246,BU-9258,BU-9273,BU-9274,BU-9275,BU-9276,BU-9278,BU-9282,BU-9283,BU-9285,BU-9286,BU-9287,BU-9288,BU-9292,BU-9293"

Any ideas?

Creating project automation to keep a table of meta data of project information synchronized with the actual project information - i.e. we have a schema of project objects, and there are objects (projects) created when a project is created. If someone goes in to edit a project (lead or key) this needs to be synchronized into Insight to support other usage of the Project Schema - driving automatic routing of project access requests. I have a webhook listener that is triggering a call based on project updates to a project automation that in theory should be updating the looked up insight objects. The correct object is looked up in automation, however it's not updateable as would be expected in the step. This makes no sense!

This is extremely impractical! This needs to be fixed ASAP!

+1 waiting impatiently  

@Miguel Angelo I believe that the v{person} is the api version. It seems that 1 works there. So it would be v1.

Hello Swati Kahol, 

Thank you for the workaround, could you clarify what 'v{version}' in the post URL is referring to?

Regards,

Miguel.

To edit the Insight attributes with more than 1 value, worth giving the below workaround a try while we wait for this feature to get released:

Use the Create object REST API with the Send web request action.

Here is an example from my test site, I have the users captured in the Jira multi-user picker field customfield_10003, here is how I have set up the Automation rule to create an object that copies the multiple users from Jira user picker to Insight user attribute:

{
  "objectTypeId": "13",
  "attributes": [
    {
      "objectTypeAttributeId": "84",
      "objectAttributeValues": [
        {
          "value": "{{issue.key}}"
        }
      ]
    },
    {
      "objectTypeAttributeId": "100",
      "objectAttributeValues": [{{customfield_10003.accountId.asJsonObject("value")}}]
    }
  ]
}

Please may this be added ASAP, the lack of this functionality is currently a big blocker to our insight implementation. 

Any news on this? There are very compelling use cases for this as outlined by Ariel, above. We want to use this for a similar scenario.

This is still not! please expedite!

This is needed asap! We are unable to continue project without it. Seems a basic facility to have as well.

Absolutely the same use case as Ariel, above. Please implement this.

This feature is really usefull, because in Server app we use it, and we are loosing an importan Feature.

We have a "New Employee" request type, and we using a Jira Insight Field called "Applications" on creation from wich we select a multiples objects from object App that we have in an Insight Schema. Then when the Issue is closed, the automation Creates a New object User, filling the atribute "Applications" that is located on User Object.

We can't do it anymore.