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

This section is only visible for Jira Service Management projects.

Request Type

The selected value will be used as the default request type when creating requests in JSM projects.

 

Software Project configuration

Epic Label

The value set will be used when creating ‘Epic’ issues, using the provided value as the epic label.

 

Epic Link

The selected issue will be used as the ‘Epic’ issue when creating issues.

For more info about setting an Epic Link dynamically see the following page: Deprecation of Epic Link, Parent and Parent Link Field Directives for inbound Issue creation and outbound notifications

Board

The selected board will be used as the chosen board for created issues.

 

Sprint

The selected sprint will be used as the chosen sprint for created issues. Requires a selected board to choose available sprint(s).

 

Content Headers

This section is used to define when content headers should be applied to Issues.

Issue Create Header

Defines when/if the Content Header should be applied during Issue Creation. Current Options are:

  1. Don’t add header - Content Header will never be applied during Issue Creation.

  2. Add header for email users - Content Header will only be applied for Email Only User (Does not have a Jira account) senders.

  3. Add header for email users and Jira Watchers - Content Header will be applied for both Email Only Users and Jira Users.

Issue Comment Header

Defines when/if the Content Header should be applied when commenting on an issue. Current Options are:

  1. Don’t add header - Content Header will never be applied during Issue Creation.

  2. Add header for email users - Content Header will only be applied for Email Only User (Does not have a Jira account) senders.

  3. Add header for email users and Jira Watchers - Content Header will be applied for both Email Only Users and Jira Users.

Comment configuration

This section is used to configure the visibility for comments.

Comment visibility

Allows setting of a default comment visibility level that will be attempted to be applied to all comments created via the related project mapping.

The setting is inherited from the mapping level above by default (rule inherits from mapping, mapping inherits from default mapping). However, you can choose whether to leverage this inheritance or not, depending on your use case.

Service Project Comment Mode

When a Jira Agent comments on a service project issue, this setting will resolve the comment visibility. Available options are:

  • Internal - The comment will be set as internal. Customers will not see the comments.

  • Public - The comment will be public, available for Customers to see.

Comment Count Limit

Default value: Unlimited. The numeric value provided will be used to reject incoming emails adding a comment to an existing issue if the comment count exceeds the provided value.

If the additional checkbox is checked, unlimited comments will be allowed.

Comment Count Limit Reached Action

If the comment count is reached, the following operation will occur.

Possible actions are:

  • Drop - The email will be dropped.

  • Forward - A forward notification will be sent to the configured forward users (See Profile Configuration | Forward User Email Addresses

  • ).

  • Ignore - The email will be ignored. Note: This may cause a mail processing loop if the ignored mail is left unread in your message source mailbox.

 

Custom Field Defaults

If a custom field is used for multiple projects, you may not be able to set a Jira custom field default value that is desired for all projects. JEMHC custom field defaults allow default values to be added to custom fields on a per-project setting. For more info see: Custom Field Defaults

To provide a default value, fill in the required field. The value will be used unless another field setting overrides the default (E.g. an @ directive can override default values).

Workflow Advance

When certain conditions are met from an incoming email, JEMH Cloud can trigger issue workflow transitions. The workflow advance mapping defines when the transition should be applied based on matching criteria, along with the transition that should occur.

For more info see: Workflow Advance mappings

Related Articles