Email This Issue
📈 Marketplace❓ Support❤️ Feedback🏠 META-INF Apps
Email This Issue - for Jira Cloud
Email This Issue - for Jira Cloud
  • ⬇️Overview
  • Email This Issue - for Jira Cloud
  • Features
  • How Email This Issue Works
  • Secure the email channel with Email This Issue
  • Comparing Email This Issue and Jira Cloud
  • 📤Outgoing Emails
    • Outgoing emails overview
    • Manual emails
      • Configuring manual emails
      • Sending manual emails
    • Email notification schemes and email notifications
    • Workflow post functions
    • Advanced email configuration
    • Customizing email templates
    • Canned Responses (default messages)
    • Scope evaluation
  • 📥Incoming Emails (Mail Handlers)
    • Incoming emails overview
  • Mail handlers - adding / editing
    • General handler settings
    • Filtering
    • Finding issues
    • Setting up rules and actions in the actions editor
      • Adding/editing actions
      • Adding recipients to Request Participants
      • Creating an issue
      • Updating an issue
      • Setting field values
      • Adding comments
      • Sending auto-reply emails
      • Executing workflow transitions
      • Creating a customer
      • Using split regexp
      • Conditions
      • Approve request
      • Decline request
    • Maintaining email chains
    • Mail Handler New UI
  • Global Sender Address Filters
  • Attachment Filters
    • Regular Attachment Handling Deprecation
  • 🤓Administration
    • Outgoing Mail Connections
    • Alerting via Webhooks
      • Webhooks
        • Configuring Slack to receive alerts via webhooks
        • Configuring OpsGenie to Receive alerts via webhooks
        • Configuring Microsoft Teams to receive alerts via webhooks
      • Webhook execution logs
    • Mail Queue
    • Email Audit Log
    • Permissions
    • Recipient Restrictions
    • Incoming Mail Connections
    • Email Security
    • Incoming Mail Queue
    • Incoming Mail Log
    • OAuth2 Credentials
      • Enabling OAuth2 Authorization in your Google Account
      • Enabling OAuth2 Authorization in your Microsoft 365 Account
      • Troubleshooting guides for Microsoft OAuth2 Connections
        • How to fix "BAD User is authenticated but not connected" error​
        • How to fix "401 Unauthorized" error
        • How to fix "key expires_in " error
        • How to fix "Need admin approval" error
  • ☁️Server to Cloud Migration
    • 🛫Server to Cloud - Automatic Migration tool
      • Preparing for the migration
      • Doing the migration
      • Finalizing the migration in Cloud
      • Migration with unsupported Jira versions causes errors
    • Server to Cloud - Manual migration guide for Email This Issue
  • ❓FAQ
    • No recipients error in outgoing emails
    • How-to add custom macro to email Template?
    • Why cannot I select custom event types in notification?
    • How to configure the Email This Issue addon user in Jira Cloud?
    • I get an error: Could not create request on behalf of the sender
    • Why is the Incoming Mail Queue size limited?
    • Outgoing mail not sent - Read timeout error
    • Access restriction icon is not appearing when adding internal attachments via Email this Issue
  • 🌪️General
    • Release Notes
    • API
      • API for Velocity Context Objects - 1.7
      • API for Velocity Context Objects
    • Addon Pages
      • Integrity Check
      • Feedback and Support
    • Security Advisories
      • Email This Issue Security Advisory September 28, 2020
    • Appendix
      • Supported Time Zones
    • Integration of Glass Documentation
Powered by GitBook
On this page
  • Sub condition
  • Issue exists / Issue is NOT found
  • Check if any of the finders fit an issue in the system
  • Check if an issue is previously created by the Mail Handler
  • Email content matches
  • Issue field matches
  • Sender has NO access to the issue
  • Sender is member of any of the groups
  • Sender is member of any of the project roles
  • Issue matches query
  • Email sender is unkown

Was this helpful?

  1. Mail handlers - adding / editing
  2. Setting up rules and actions in the actions editor

Conditions

Conditions helps you to add different routes to your actions.

PreviousUsing split regexpNextApprove request

Last updated 1 year ago

Was this helpful?

Sub condition

The app supports two logical operators:

  • All -> represents the AND operator.

  • Any -> represents the OR operator.

Issue exists / Issue is NOT found

The app checks if any issue exists that is related to the email. There are two behaviors of these conditions.

Check if any of the finders fit an issue in the system

This is the most common usage of this condition. In the below example, the condition checks if the finders have any issue results.

Check if an issue is previously created by the Mail Handler

In some special cases, it should be checked if an issue was previously created. The below example represents an Update issue (Set Labels) that will be executed only IF any of the above, same-level IF conditions are true. In other terms, if the email's Subject matches the regex STM.* or TEMP.* the Labels field will be set to the added Manual value. Else, if the issue already existed before, the Assignee field will be set to a Manual value.

Email content matches

This condition checks whether parts of the emails match with a given regexp.

The fields that can be set here are the followings:

Email part

  • Body

  • Subject

  • Header

  • To addresses

  • Cc addresses

  • To/Cc addresses

  • From address

  • From name

Header name

If the "Header" email part is selected, this field appears to allow defining the header's name. The header name search is case-insensitive. If the defined header is not present in the email, the result of this condition will be false.

Negation of the result

  • matches regexp -> true if the regexp fits the selected email part. Example: Email's body: "The email content." Regexp: email Result of this condition: true

  • not matches regexp -> true if the regexp does not fit the selected email part Example Email's body: "The email content." Regexp: email Result of this condition: false

Regular expression

Issue field matches

This condition checks a field of an issue.

This condition only works correctly, if you have an existing issue at this point of the execution. If there is no issue when the execution calls this condition, the result will be false.

The following fields can be set:

Field

Currently, we support only the Status field

Negation of the result

  • equals

  • not equals

Value

The Field's value.

Sender has NO access to the issue

This condition checks if the sender has permission to open the issue by checking the BROWSE_PROJECTS permission. A customer also has BROWSE_PROJECTS permission if added as a Request Participant.

If the sender has no access to the page, the action in the IF statement is executed.

For proper working please be sure if there is a find or created issue in the context.

Sender is member of any of the groups

This condition checks if the sender is a member of any of the given groups.

Sender is member of any of the project roles

This condition checks if the sender has the given project role(s) in the given project.

Issue matches query

This condition allows running a JQL query on the issue in the context.

Please make sure there is an issue in the context, where you add this condition. A good practice, if you add an "Issue Exists" condition before this one.

If the JQL should contain a user, please select "Insert user" option below.

Email sender is unkown

This condition checks if the sender has a user account on the Jira instance.

If the sender has no user account, the action in the IF statement is executed. Disabled users are handled as non-existing.

A regular expression that fits with any part of the email. Documentation can be found .

If there is no issue at this point of the execution, then the app checks the global permission of the user. For more details, please check the Atlassian .

here
documentation
An example for ensure an issue exists in the context when the JQL query called.
The read only mode of the JQL query field
Editing view of the JQL query field
Adding user ID to the JQL query field