We need to automatically send emails to approvers who get removed as an approver, to tell them their approval is no longer required. How can we accomplish this in automation?
Hi @NoName
What have you tried thus far to solve this need?
If you have an automation rule that is not working as expected, note context is important for the community to help. Please post the following:
If you have not tried creating the rule yet, I encourage you to try. Successfully using automation rules requires learning and experimentation.
To help get you started, such a rule could be triggered on a change to the Approvers field, then use the changelog / field change smart values to identify the removed approver, and then send them the notification.
Kind regards,
Bill
You can select to trigger when an Approver is deleted but I'm not seeing any option to then email that removed Approver. You can seemingly only email the Reporter, specific people, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please read the documentation on the changelog / field change smart values. When the trigger is for a field change, the prior / removed values may be accessed for use in the rule.
One challenge for your scenario is only the removed user's account ID is available. In that case, a call to the REST API will be needed to get their email address, using the Send Web Request action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I had the bandwidth to read through the documentation, I would love to. Unfortunately, when you're told to do something with having zero knowledge but it needs to be done now, I don't have that luxury. That's why I've asked here. I am a deskside technician having to setup Jira while taking care of 1000 users and 1000 devices. If I had the time to figure this out completely on my own, I would have not come here. I am asking for assistance. If you're not willing to give that assistance, that's fine but telling me to RTFM, is frustrating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I understand your frustration as learning takes time and effort. Please note this is the Atlassian Community. It is a place for people with similar interests to learn and collaborate with each other and is not a place to provide free labor and turnkey solutions to requests upon demand.
It is also not the Atlassian Support channel. If you want to contact them, please work with your Jira Site Admin to submit a ticket here: https://support.atlassian.com/contact/#/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you try to submit a ticket to Jira, they direct you here, that's why I came here. If I'd known the responses here would be the same as one would get in Reddit, I would not have wasted the time. Unfortunately, there seem to be an infinite number of values in Jira and while you might, not everyone knows them off the top of their head or can know where to even begin looking.
Sometimes, people just need a little help from a community, which is what I thought this was. Sometimes, there are people willing to share knowledge freely. The number of people who hoard knowledge is unreal as everyone needs a little help sometimes in an urgent situation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.