Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-85145

Don't allow for emails to be sent to users who are inactive/removed from a Jira site even through Automation

XMLWordPrintable

    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, if you have an automation setup to send an email to a user that is "Not Active/Removed/Deleted/Suspended" on just the Jira site the email will still be sent. This can cause a potential security risk. 

      The automation smart value  {{reporter.active}} doesn't check the Jira instance to see if a user is active or inactive so that doesn't solve the issue for Jira Automation sending an email to a user that is not on in the Jira instance but if that user's account is Active in Jira. 

      EX: Would be nice for the automation smartvalue be able to see if the user is active in the Jira instance or some other indicator to toggle that would remove the ability for the Automation rule to send an email to a user who is not Active in the Jira instance that triggered the email. 

      Related: Email notifications are sent to inactive users who own rules that have failed.

            [JRACLOUD-85145] Don't allow for emails to be sent to users who are inactive/removed from a Jira site even through Automation

            Shanelle Boluyt added a comment -

            What this means in practice:

            If your parent organization is using Atlassian Guard, and the user is deleted / disabled in your Jira / Confluence instance, this smartvalue will continue to see the user as "active" even though they are NOT active for the instance in which you are writing an automation.

            Shanelle Boluyt added a comment - What this means in practice: If your parent organization is using Atlassian Guard, and the user is deleted / disabled in your Jira / Confluence instance, this smartvalue will continue to see the user as "active" even though they are NOT active for the instance in which you are writing an automation.

              Unassigned Unassigned
              f6045dee6456 Gavin Bramley
              Votes:
              4 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: