Versions Compared

Version Old Version 5 New Version Current
Changes made by

Ryan Clifton

Mike Harrison

Saved on

Key

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

...

Working Flow

Non working flows

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

This flow only allows the JEMH Application User JEMHC application user to create issues in Software Projects.projects

This flow only allows the JEMH Application User JEMHC application user to create issues in JSM Projects.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

Identify if JEMHC

...

app user has the relevant product access

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

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

Code Block
https://Base-UrlURL/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 Groupsuser’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

...

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

  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.png

  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.png
Info

If you have you’ve changed the default groups that provide product access, then they will they’ll 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 app user lacks a group for relevant product access, uninstall and reinstall the app via Manage Apps to recreate the user, which will grant appropriate 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 resolvedus for support.

  • 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

  • .