Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Insight Automation Email Notification: Recipient By Attribute

I was reviewing https://documentation.mindville.com/insight/latest/insight-automation-33467001.html#InsightAutomation-Emailnotification

And I'm finding that there is no explanation whatsoever of how to use the "Recipients By Attribute" field.

That field seems to imply we can get a recipient from an object attribute, but that seems to go directly against the note "At least one of the two email related fields (Jira Recipients, External Recipients) must contain valid values".

My particular use case is that I have an Owner attribute on the object that I want to trigger an email from. This attribute is an object reference to a User object type. The user object type has both Email and Jira Account attributes.

Can I, somehow, with this configuration, send an email to the owner of my object when my IQL rule is true?

What would be nice is if I could select the recipient with Owner.Email

 

1 answer

In an automation rule, you will only be able to use attributes from the object that triggered the automation. As the Email attribute you want to use belongs to another object type, it is not possible to do the way you want. (would be really good if it was possible though...)

A workaround would be to make sure that the automation rule is triggered by the User object instead. Unfortunately you will not be able to send any information about the connected object in the email - only attributes from the User will be available in that case. 

For example, if your object type is called Service, you could trigger a rule every hour on Users connected to a Service object with certain conditions. Set up a scheduled event with an IQL like this objecttype=User AND object HAVING inboundReferences(objectType = Service AND Status="Take action") 

Thanks @Björn Gullander 

I already make extensive use of groovy automation.
I think that would be a cleaner implementation for me.

I mostly wanted to understand that built-in feature and its limitations.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - April 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

316 views 3 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you