Automatically create new user type Assets objects based on your tickets reporters
プラットフォームについて: Cloud のみ - この記事は クラウド プラットフォームのアトラシアン製品に適用されます。
要約
This article describes the steps to automatically create user type Assets objects based on your ticket's submitters. It could be useful in case you would like these user objects to be referenced into other object types created in the future.
Pre requisites
You will need an existing object type with at least one user attribute type, just like the following example:
ソリューション
Our solution requires an automation rule to be created. The automation rule structure should be as follows:
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 submitters account ID in order to avoid duplicates:
警告
The items highlighted above (User and Jira User) should be filled according to your object type name and object type attributes. I've used the above information based on the object type I've previously created (refer to the Pre requisites section).
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 (note that the second value refers to my attribute name which is Jira User, in case you've used another attribute name you should update it accordingly):
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 like the following example:
