/
Issue configuration

Issue configuration

Owned by Denny Miller
Last updated: Oct 09, 2024 by Phil Evans
6 min read

The Issue section allows specific Issue field configuration to set default values for Jira fields and custom fields.

 

Configuration

Operating Mode

The operating mode defines how the Project mapping should operate. If an inbound email operation type does not match the operating mode, the email will be forwarded/dropped based on the chosen ‘failure action’

The following options are available:

  • Create and Comment - The project mapping will be applied for both issue create and issue update emails.

  • Create Only - The project mapping will be applied for only issue create emails. Emails associating to an existing Issue will not be handled.

  • Comment Only - The project mapping will be applied for emails relating to existing Issues.

    • When ‘Comment Only’ is selected, an additional ‘Failure Action’ option will appear. The action can be set to:

      • ‘Drop’ (Incoming messages not matching will be dropped and ignored).

      • ‘Forward’ (Incoming messages not matching will be dropped and ignored).

 

Issue Association By Email Address

When enabled, the catch email address recipient address will be checked for an Issue Key. E.g. ABC-123@company.com would comment on the issue ABC-123. See https://thepluginpeople.atlassian.net/l/cp/F6Uh3YHh for further information.

 

Default Summary

When an incoming email does not contain a subject, the value set will be used as the issue summary when creating issues.

 

Description

When enabled, the value provided will override the incoming email body as the issue description.

If you wish to use the incoming email body, this setting must be left empty.

 

Issue Type

The chosen Issue Type will be used when creating issues for the mapped project.

 

Sub-Task Issue Type

The chosen Sub-Task Issue Type will be used when creating issues for the mapped project when a parent issue key is provided (e.g. providing parent issue key using directive: @parentIssueKey=ABC-123).

If the project doesn't have sub-task types, select 'None'

 

Components

This setting allows you to specify components for created issues.

 

Priority

The selected option will be applied as the default ‘priority’ for created issues.

 

Security Level

The selected option will be applied as the default ‘security level’ for created issues.

Ensure that Project Role (atlassian-addons-project-access) is added to the security levels you wish JEMHC to be able to set. We prevent retrieval of security levels not associated to this role for security purposes.

Labels

Any labels specified in this setting will be applied to created issues.

You can add multiple labels by separating values with a comma. E.g.: my-first-label, another-label, final-label

 

Due Date

The numeric value selected specifies the days left until the issu ‘due date’ for created issues. E.g. 14 would set the due date in 2 weeks.

 

Exclude Email If Issue Apply JQL

When configured, matching JQL will exclude comments from being added if the associated issue matches your JQL. This setting allows issues matching specific criteria to disallow additional comments (E.g. status in (Done, Closed) to prevent comments on closed issues).

See Further JQL documentation to help configure your JQL exclusion.

 

Exclude Email If Issue Apply JQL Action

When your JQL matches an issue, this setting specified the operation that will be performed if incoming emails attempt to add comments to Issues matching JQL. The possible actions are:

  • Forward - The incoming mail will be forwarded to your chosen forward user addresses.

  • Drop - The incoming mail will be dropped.

  • Ignore - The incoming mail will be ignored.

 

Use Mail Header Priority

When enabled, JEMHC will check the incoming mail headers for a X-priority header. If found, the Jira priority found will be applied. For more info about how to use see: Use X-Priority Headers

 

Service Project configuration