...
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. |
|
|
|
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:
Go to JEMH > Tools > User Finder and search for “Enterprise Email Handler for Jira (JEMH)”. Copy the Account Id as this is needed later.
Go to (cog) > User Management > Users and select “Show Details” on a random user.
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:
|
Required Groups for providing Product Access:
The groups that this user is added to will depend on the products that are installed.E.g.
If you have only Jira Software installed then only
jira-software-users-BaseUrl
/jira-users-BaseUrl
will be required:If you have both Jira Software and Jira Service Management installed then both
jira-software-users-BaseUrl
/jira-users-BaseUrl
andjira-servicemanagement-users-ryan-access-testing
are required:
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:
|
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. |