nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Smart value - Email to "Alarm owner"

Paul Ceronio_kpmx1s

Good morning,

We are in the process of setting up an alarm automation that creates an Issue when a contract in our asset database reaches the "Cancelation date" defined in its attributes. We have also defined an "Alarm owner" to whom the Issue should be assigned.

What automation steps should I implement to assign the issue to the Alarm owner?

I am not familiar with User Defined Fields yet, so I'm trying to create an Automation in a "Contracts" project that should assign newly created Issues to the "Alarm owner".

My automation currently looks like this (a bit primitive, but I'm still working on the IF condition).

(Translated from German:)

Is the Smart Value in the THEN condition correct and can it be used that way?

The "Alarm owner" attribute is defined like this:

("Employees" points to our Employees Object Scheme)

Thanks in advance

Paul

Accepted answers

Paul Ceronio_kpmx1s

Hi everyone,

I've now created an "Alarm owner" custom field that displays the User in the Issue created via Assets Automation:

Is there an automation rule that will allow me to assign the Alarm owner to the ticket from here? I cant find any field outright in the Project automation rules, maybe there is a smart value for it?

Thanks again for any advice!

Paul

All comments

Chrissy Clements

Hey @Paul Ceronio

I'd suggest a scheduled automation that performs a lookup on the CMDB, you can then access the list of objects returned by the lookup action.

Here is a sneak peek at one I use to create reminders for the team to review their IT DR Plans.

I used this help docco to get started: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-insight/#SmartvaluesInsight-Lookupobjects

Screenshot 2024-07-12 at 9.57.59 AM.png

Paul Ceronio_kpmx1s

Hi Chrissy,

Thanks very much for your suggestions.

Unfortunately, we use Jira Data Center - I'm starting to discover that a lot of the options and functions available in the Cloud have not been implemented in the Data Center version 😭. Scheduled automations are not implemented as far as I can tell.

We're implementing a workaround involving creating an Incident using Assets Automation and (hopefully) assigning it using project automation:

I've reconfigured the "Alarm owner" as type "User" and value type "Jira Agent".

If anyone can tell me what Project automation rule/smart value to use to assign the Incident created to the Alarm owner, I'd be extremely grateful!

Kind regards,

Paul

Adolfo Casari

@Paul CeronioI use DC (9.12) and scheduled automations are available under Automation.

For the other actions you should use REST API and Web Request action. If you have Scriptrunner then there are some extensions to the standard actions to deal with Assets data.

Carla Ann Rowland

Hi Paul:

This is just broad strokes, for data center,

you need to establish the reference between the table where the contract owner field is and the employee table.
and in the employee table pull the JIRA user data and set is as value in assignee field.

If I get a chance I will try to get back to you with more clarification

Paul Ceronio_kpmx1s

Hi everyone,

I've now created an "Alarm owner" custom field that displays the User in the Issue created via Assets Automation:

Is there an automation rule that will allow me to assign the Alarm owner to the ticket from here? I cant find any field outright in the Project automation rules, maybe there is a smart value for it?

Thanks again for any advice!

Paul

Paul Ceronio_kpmx1s

Thanks so much for the different ideas and input. In the end we assigned the Alarm owner using a Workflow post-function rule.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-desk-data-center

jira-service-management-server

jira-service-management-data-center