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
  • Examples
  • Evaluation

Was this helpful?

  1. Outgoing Emails

Scope evaluation

PreviousCanned Responses (default messages)NextIncoming emails overview

Last updated 2 months ago

Was this helpful?

There are a few configuration items in Email This Issue that are configured with Projects, Issue Types, or a JQL filter. They make up the scope.

The following settings have scope:

When Email This Issue searches for the best matching of the above entities, it evaluates their scope. The order of evaluation is specified as described examples in the following. In all screens where these entities are listed, the list order corresponds to the order of evaluation.

Examples

Selected Projects

Selected Issue Types

JQL Explanation

Explanation

1

Project1, Project2

Story, Task

priority = Highest

Most important Story or Task issues from the selected projects.

2

Project1

sprint in openSprints()

Issues from the active sprints in Project1

3

Task, Sub-task, Epic

All stories, epics or sub-tasks from all projects

4

project in (Project1, Project2) AND type in (Story, Bug) AND text ~ "Security" OR project in (Project3, Project4) AND type = Epic

Stories or Bugs related to "Security" in their title or description from Project1 and Project2. All Epics from Project3 and Project4 - while this part is in the JQL, Epic as an issur type is already present in Scope 3 with no restrictions, so Scope 3 will be applied instead of this scope.

5

All issues in Jira. It is perfectly valid to keep project, type and JQL empty. It will serve as a default configuration for issues not having a better matching scope.

Evaluation

Scoped entities are evaluated in the order they are listed. Those that are configured with projects or types are evaluated first, then those that have JQL criteria, and finally the default ones.

Examples for Scope evaluation:

Issue

Matching Scopes from the above table

A Story issue that is in an active sprint in Project1 with priority Highest

Number 1

A Story issue that is in an active sprint in Project1 with priority normal

Number 2

An Epic issue from Project3

Number 3

A Story issue from Project2 with the word "security" in its summary with Medium priority.

Number 4

A Story issue from Project2 not related to "security" with Low priority.

Number 5

A Bug issue from Project3

Number 5

📤
Manual Email Configuration
Email Notification Schemes
Advanced Email Configuration