Project Settings configuration

Summary

Within the Project Settings configuration you are able to access a Project specific view of the JEMHC configuration which will allows Project Admins the ability to adjust the JEMH configuration that relates to that specific Project. Note: This section has very limited options when compared to the Jira Administrators view.

This can be accessed by going to Project > Project Settings > Enterprise Mail Handler (JEMH)

Blocklisting

The Blocklisting tab allows you to modify and create exclusions that are scoped for that project. Blocklists that are scoped for all Projects (Global) can only be modified by Jira administrators that have access to the main JEMH Configuration.

For more info about Blocklisting see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/3782115329

Static Resources

Here is where Project Admins can view the Static Resources that have been scoped for this Project. This will display items that have a scope of Global and to that specific Project. Note: Items with a scope of Global can only be viewed and cannot be modified as they can affect other Projects.

For more info about Static Resources see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/161419513

AdHoc Configuration

Here is where you grant users permission to use JEMH Ad-Hoc notifications. Here you are able to configure either project specific permissions or Global permissions which would apply to all project.

For more info about Adhoc notifications see: https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/29655110

Test Cases

Test Cases allow you to test whether the Profile is configured correctly as per your needs. Here you are able to view, edit and create Test Cases for that particular Project allowing Project Admins to test the profile configurations. Note: Profiles can only be selected if they contain a Project Mapping for this Project.

Test Case actions

Run (Play button)

This will process the Test Case using the select profile.

Configure Profile (Cog Icon)

This will open the Profile within the Jira Admin page. Only Jira Admins can use this option.

Edit

This opens the Test Case editor.

Copy

This creates an identical copy of the selected Test Case.

Export

This downloads a txt file of the Test Case email.

Auditing

The Auditing page within Project Settings allows Project Admins to view the emails that either created an issue within the project or that attempted but failed to create an issue within the project.

For more info about auditing see:

Search Options

Search Method

This defines the value to search for within the Audit results. Current options are:

  1. ID - Searches using the Audit Record id

  2. Issue Key - Searches using the Issue Key

  3. Sender Address (From) - Searches based on the Sender Email Address

  4. Status - Search based on the Status of the audit record.

  5. Outcome - Search based on the Outcome of the audit record

Not Before

Defines the date of audit records to show from.

Not After

Defines the date of audit records to show to.