Automations based on asset expiry fields.

[Jamien Price]

Hi all,

We've recently built a CMDB in Jira Assets. We'd now like to mature our processes with automations based on those assets. When we first looked at assets a year ago we thought our goals were possible but now I'm seeing a lot of dialogue claiming automations with assets is actually very limited. Can anyone confirm what parts of the following is possible?

1. User requests a license via a "license request" Jira ticket.
   1. that request type will capture if the license is permanent or temporary and if temporary capture an end date.
2. Automatically create a new asset in our "Software Licenses" using the fields we captured on the ticket.
   1. Create the asset with a "status" attribute set to "license requested".
3. Once the Jira ticket is set to "license assigned" status have the corresponding asset change its status attribute to "assigned".
4. If the license had an end date create a new ticket once that end date comes to remove the license (or ideally change the status of the original ticket to a "remove license" status)
5. Or if the license was permanent generate a new ticket every 12 months to remind a technician to check if the license is still needed.

We're on cloud based JSM with a Premium license if that matters.

Thanks!

[Marc - Devoteam]

Hi @Jamien Price 

1. Yes , if the fields on the issue have a value, and the assets object type to be created has attributes to store this information an automation rule can accomplish this
2. Yes, if you have a status attribute on the object type you want to create and the status "license requested" is available as an option
3. Yes and automation rule can be activated on the transition to find the related object and edit the status attribute of the object
4. Yes, again a scheduled automation rule on a daily basis that checks the end date attribute and creates a new ticket or transitions the old ticket to a new status, but this will require that there is information stored on the asset object that defines the issue, like the issue key
5. Yes ,same as above. Suggestion is to always set a date attribute and check in the automation on another attribute to have on the object that is also a status attribute to capture if the license is permanent or temporary

Premium doesn't matter, you would have to be otherwise you wouldn't have the Assets feature.