Common errors and solutions

Owned by GCLogix Admin
Last updated: Sept 24, 2020
3 min read

This document lists out all the common errors one (admin) might face while using the “User Management for Jira Cloud“ app.

1. Validation Error:

Reason:

One (admin) might face this error while trying to execute any of the functionalities provided in the app “User Management for Jira Cloud“ without validating their credentials.

Solution:

  • Go to main page

  • Click on Validate button under Configuration

  • Enter the right Email and API Token

  • Click on Validate button

  • Once successful, this error will be resolved

2. License Expired:

Reason:

One (admin) might face this error when they open or navigate to the app because of license expiration.

Solution:

Buy a license for the app to resolve this error.

3. Cannot add an user to the group:

Reason:

One (admin) might face this error when they are trying to add user(s) to a group and the reason being that, the user that one (admin) is trying to add might already be a part of the group or maybe the user(s) that one (admin) is trying to add may not exist in the instance at all.

Solution:

First, check if the user(s) exists in the instance, if one (admin) isn’t able to add then that’s because the user(s) is already part of that group.

Second, if the user(s) doesn’t exist in the instance, then create the user(s) and then add them to the group.

This will resolve the above error.

4. Cannot remove user from the group:

Reason:

One (admin) might face this error when they are trying to remove user(s) from a group and the reason being that, the user that one (admin) is trying to remove might not be a part of the group or maybe the user(s) that one (admin) is trying to remove may not exist in the instance at all.

Solution:

First, check if the user(s) exists in the instance, if one (admin) isn’t able to remove then that’s because the user(s) is not part of that group.

Second, if the user(s) doesn’t exist in the instance, then it is obvious that they cannot be removed from the group.

This will resolve the above error.

5. Cannot create a group:

Reason:

One (admin) might face this error while creating new group(s) because of the reason that, the group(s) one (admin) is trying to create might already exist in the instance.

Solution:

Check if the group(s) already exists. Adding duplicate values (i.e group(s) names) while creating will throw the above error every time.

6. Cannot delete a group or specified group does not exist:

Reason:

One (admin) might face this error while deleting group(s) because of the reason that, the group(s) one (admin) is trying to delete might not exist at all.

Solution:

Either the group(s) one (admin) is trying to delete doesn’t exist in the instance or there might be mismatch in the group(s) names that are being passed. Providing correct names or values of group(s) should resolve the above error.

7. Cannot create a user:

Reason:

One (admin) might face this error while creating new user(s) from the app “User Management for Jira Cloud“, because of the wrong format entered (i.e not passing values as mentioned in the document)

Solution:

Please check the document to understand the right format needs to be passed in order to create user(s). Once the right format is passed, user(s) can be successfully created and one (admin) will not face the above error.

8. Cannot delete a user or specified user does not exist:

Reason:

One (admin) might face this error while deleting user(s) in their Jira instance because of multiple reasons.

  • The user(s) or accountId(s) that one (admin) is trying to delete is an assignee or reporter of an issue or multiple issues

  • The user(s) or accountId(s) that one (admin) is trying to delete might not exist in the instance at all

  • There might be mismatch of accountId(s) that are being passed to delete

Solution:

  • If the user(s) that one (admin) is trying to delete is an assignee or reporter in an issue or multiple issues then change the assignee or reporter of those issues to some other valid user that one (admin) will not delete

  • If the user(s) doesn’t exist in the instance in first place then one (admin) cannot delete them

  • Make sure that the accountId(s) being passed are valid