Creating Profiles

1 Summary
- 1.1 Creating new Profile
- 1.2 Create Form Fields
  - 1.2.1 Name
  - 1.2.2 Description
  - 1.2.3 Project
  - 1.2.4 Issue Type
  - 1.2.5 Readiness
  - 1.2.6 Forward User Email Addresses
    - 1.2.6.1 Creating a profile without valid forward notification configuration
  - 1.2.7 Catch Email Addresses
2 Related Articles

Summary

Profiles control how messages from an inbound message source are processed. Per-project configuration is done through Project Mappings inside a Profile.

Creating new Profile

To create a new Profile from scratch you will need to go to Profile > Create.

This will then show a form which needs to be filled in.

Once saved this will result in a new Profile being created which can now be used to create issues or comment on issues within the Default defined Project. See the relevant pages within JEMH Cloud Profiles section for more info about Profile Customisation: Profiles

Create Form Fields

Below are some explanation as to the fields that need to be filled in.

Name

This is the name of the Profile

Description

This Describes the Profile’s purpose if needed.

Project

This is the Default Jira Project for emails to be routed to. More Projects can be added later through the use of Project Mappings. See following page for more info about Project Mappings: Project Mappings

Issue Type

Shown once a Project has been selected. This is used to define the default Issue Type that issues should use when they are created. This can be customised after Profile Creation.

Readiness

This is used to help administrators organize profiles.

Forward User Email Addresses

This identify human contacts that should be notified for specific events such as processing failures, bounces etc. Used when any actions are “Forward”.

You must have a valid message outbound configuration to send ‘Forward’ notifications.

Please see Message Outbounds (Email) for creating message outbounds.

Creating a profile without valid forward notification configuration

As mentioned above, a valid Message Outbound must be configured if you intend to send forward notifications.

If you do not create a message outbound, the default action will be set to ‘drop’, which will result in the polled mail being dropped during the error scenarios.

At present, the following settings allow ‘forward’ action to be set. Without a message outbound, these settings will default to ‘drop’:

Non Catch Email Action
Profile Blocklist Action
Global Blocklist Action
Non Delivery Email Action
Error Outcome Action
Precedence Bulk Action

(After creating a valid message outbound, the default will return to ‘forward’ for new profiles, and existing profile operations can be changed only when a valid message outbound is configured. An error alert will be shown if the message outbound is no longer valid, indicating that forward notification scenarios will fail without a valid message outbound).

Catch Email Addresses

Inbound emails are only processed if one of the recipients match a catch email address. Multiple addresses can be defined using a comma-separated list and regular expressions can be used to describe a range of addresses. To prevent loops, notifications won't be sent to addresses matching any configured catch email address.