Hi @Rob. I know this is possible in Slack using smart values, but I haven't tried it with Teams. For Slack, I use smart values such as: { {issue.Time to Resolution.ongoingCycle.goalDuration.friendly}} - time goal of the TTR SLA. { {issue.Time to Resolution.ongoingCycle.elapsedTime.friendly}} - elapsed time of the TTR SLA. For Jira Service Management only. Learn more about Assets in Jira Service Management. This condition checks if an Assets object or an issue's Assets field matches the AQL query. You can either search based on objects, or Assets fields on an issue. To select the Object tab, your rule must have the Object trigger. I tried to run a simple regex in my automation but the output was blank despite the pattern working as expected. What solved the issue for me was to add a capture group to my pattern. My pattern that was returning an empty set: " [\w-]*$". My pattern that works as expected: " ( [\w-]*) $". You might achieve the desired result by changing. In "Additional fields" you need to clear the example values and then insert the code Ravi suggested. You can see above how it should look like. You have to use advanced edit to get the account id of the user from the people field. Try this to set the assignee. Use an appropriate Proforma smart value, for example for a text field, use: {{issue.properties."proforma.forms.i1".state.answers.AAA.text}} AAA is the Question ID, which you want to locate. To check each question, to verify which ID relates to which, create a smart value line for the number of questions you have - so I had 15 on my form, thus Create automation e-mail with portal url, rather than jira. Is it possible to setup an automated e-mail with a smart value for the customer portal URL to the issue? I've used { {issue.toUrl}} and this will take them to the issue, but it's using the interface of that the agents see. Since this e-mail uses smart values is there a smart value for Navigate to the field value you want to display in your rule and click on the field. Then copy the ‘dot notation’ in the footer: In this example, the priority field is selected, which means the smart value is { {issue.fields.priority.name}} however, the fields section is not required so you could just use { {issue.priority.name}} or shorten Make sure that your team is working on the right requests at the right time with easily configurable service project queues. A queue is a filtered set of issues that are displayed to your team. Use your project's default queues or create custom queues to save time triaging requests, and to give your agents more visibility of the number and type DirLl.