/
Configure JSD Customers for use with JEMH

Configure JSD Customers for use with JEMH

Owned by Former user (Deleted)
Last updated: Jun 26, 2019 by Mike Harrison
2 min read


Summary

You wish to configure JEMH to facilitate email creation and commenting in JSD projects by Customer Users (which are created automatically).

Important notice

Newer versions of JEMH do not require any of the customer user set up shown on this page. Versions equal to or higher than those in the below table do not need customer user set up:

Jira version range

JEMH Server version

JEMH Data Center version

Jira version range

JEMH Server version

JEMH Data Center version

7.10.0 - 7.13.4

2.7.42

2.7.43-dc

7.8.0 - 7.9.2

2.6.21

2.6.22-dc

7.7.0 - 7.7.4

2.5.18

2.5.19-dc

7.6.0 - 7.6.13

2.4.19

2.4.20-dc

More information can be found here: Jira Service Desk compatibility improvements

Customer User Configuration

  • A user group should be created that is only for JSD customer users.  In this example we have named it customer.

  • This customer group must:

    • Be assigned the Project Role Service Desk Customers by going to the project's Users and roles section

    • Be granted issue permissions that are appropriate for customers

      Example customer permission configuration

Do not grant customer users or the customer user group the "Service Desk Agent" permission as this will cause problems with comment privacy. Similarly, do not give Agent users membership of the "Service Desk Customer" project role.



Profile Configuration Changes

Profile>User

  • Your JEMH profile should have a Default Reporter selected.  This user should have all non-admin issue permissions and also be a Service Desk Agent.  Note that customers must not have Service Desk Agent permission.

  • If you want new customer users to be automatically created when an existing account is not found for the sender address, enable Create users and enter the name of the customer user group that you have created under Auto Join Group(s)

Profile>Security

  • The setting Treat Unprivileged Users as Non-JIRA should be enabled

Related Articles