Automatically create new user type Assets objects based on your tickets reporters

Summary

This article describes the steps to automatically create user-type Assets objects based on your ticket's submitters. It could be useful if you want to reference these user objects in other object types created in the future.

Solution

Our solution requires an automation rule to be created. The automation rule structure should be as follows:

Prerequisites: You will need an object type with at least one user attribute type

Step 1: The automation trigger should be Issue created so that it executes whenever a new ticket is submitted.

Step 2: Now we need a Lookup objects action to search for already existing objects based on the submitter's account ID in order to avoid duplicates. The AQL search can be like: objecttype = 'User" AND "Jira User" = "{(reporter.accountld}}"

Step 3: The next step will be an Advanced compare condition with the lookup objects action's results. In case an object already exists for the ticket's submitters we don't want to proceed and create a duplicate object, so we will need a step like this: {{reporter,accountid}} does not equal {{lookupObjects.Jira User}}.

Step 4: And in case the above condition matches it means that there's no object created for the ticket's reporter yet, so we can include a Create object as the automation's next step which will create the actual user object:

Step 5: The final result will be a new object created.