Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Working Flow

Non working flows

This flow allows the JEMH application user to create issues in both project types

This flow only allows the JEMH Application User to create issues in Software Projects.

This flow only allows the JEMH Application User to create issues in JSM Projects.

  1. Installed Jira software

  2. Installed Jira Service Management

  3. Installed JEMHC

  1. Installed Jira Software

  2. Installed JEMHC

  3. Installed Jira Service Management

  1. Installed Jira Service Management

  2. Installed JEMHC

  3. Installed Jira Software

Solution

The solution is to manually grant the JEMH application user access to that new Product. However, since the application user is hidden from User Management page it means that you have to follow the steps below to access the JEMH application user profile and grant them access:

  1. Go to JEMH > Tools > User Finder and search for “Enterprise Email Handler for Jira (JEMH)”. Copy the Account Id as this is needed later.

    1. Screenshot from 2024-05-16 08-56-10.pngImage Removed
  2. Go to (cog) > User Management > Users and select “Show Details” on a random user.

  3. Modify the URL by removing all of the digits after “users/” and replace this with the copied Account Id for “Enterprise Email Handler for Jira (JEMH)”.

Below is a screenshot of a example URL. The orange rectangle is the section of the URL that needs to be changed.

...

Once the above steps are complete you will have access to the JEMHC application users Profile and you will be able to grant the Application User access to the required Products by pressing “Add Products”.

Once completed the Application User Profile will look similar to the below example:

...

Identify if JEMHC Add-on user has the relevant product access

The easiest way to identify if you are affected by this issue, of JEMHC not having Product access, is to view the groups that the JEMHC Add-on user currently has. Currently, this can only be done by using the Jira Cloud Rest API to gather a specific User’s groups, as Atlassian does not allow add-on users to be viewed within User Management.

For example using the below Rest API Url: (will need to replace “Base-Url” with your specific Jira cloud URL):

Code Block
https://Base-Url/rest/api/2/user/groups?accountId=557058:1aad7a42-0087-42dc-9dda-6674a94917d9
Info

Notes:

  1. Your current logged in user must have the relevant permissions for viewing User’s Groups

  2. The account Id (557058:1aad7a42-0087-42dc-9dda-6674a94917d9) within the above URL may not be correct. To identify the correct account Id, you can use the JEMHC Find User feature and then replace the above Id. For more info about this feature see: User Finder

Required Groups for providing Product Access:

The groups that this user is added to will depend on the products that are installed.E.g.

  1. If you have only Jira Software installed then only jira-software-users-BaseUrl/jira-users-BaseUrl will be required:

    Screenshot from 2024-05-20 11-06-00.pngImage Added
  2. If you have both Jira Software and Jira Service Management installed then both jira-software-users-BaseUrl/jira-users-BaseUrl and jira-servicemanagement-users-ryan-access-testing are required:

    Screenshot from 2024-05-20 11-12-04.pngImage Added
Info

If you have changed the default groups that provide product access then they will need to be used instead.

Solution

If the JEMHC Add-on user does not have a group that provides access to a relevant product, then the only way to solve this would be to go to Manage Apps and uninstall JEMHC and then re-install JEMHC. As this will re-create the JEMHC user which will grant them the relevant product access.

Info

Note:

  • You may encounter JEMHC re-use Trial check if you attempt this after your trial has been used, e.g. 3 months after JEMHC was first installed. If you encounter this, then contact PPL Support to get this resolved.

  • Your configuration/data will not be removed, as this data is stored for 30 days in case you decide to re-install.

Note

The previous fix for solving issues related to JEMHC Addon User Product Access, was to manually set the product access for the JEMHC Addon user. However, recently Atlassian made a change that prevents this from occurring.