JIRA Documentation

JIRA 6.3 EAP
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

Symptoms

During the removal of a certain group(s) in JIRA user(s), JIRA would not process the command and act like there are no process done as the group membership is not removed. There are no stack traces thrown by JIRA during the whole process.

Here is a video explaining the issue in question:

Download Video

  • In order to confirm that this is the issue, please try to remove another groups on that particular user and see if it is successful.
  • This issue usually appear on a deleted user_name(s) that re-added into JIRA.

 

Cause

  1. JIRA did not completely deleted all of the necessary user rows on cwd_membership, here is the relevant bug report in regards to this issue:  JRA-25235 - deleteUser leaves stray cwd_membership records Resolved
  2. Somehow the Group have a mismapped value on the cwd_membership table on the directory_id column when there is multiple directory is connectec to JIRA.

Diagnosis and Resolution

Please Note!

Icon

Make sure that you shut down JIRA before proceeding.

Icon

Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.

Cause 1:

  1. Identify the problematic user_name
  2. Run the following SQL query against JIRA database

    The query will list down all of the membership under the problematic user_name

  3. From the result of the above steps, ensure there is a different child_id with the same directory_id before proceed to the next steps. If there are no multiple child_id, this is not the issue
  4. Remove the problematic row(s) by executing this SQL query against JIRA database

    The above command would delete all rows relevant to the offending child_id value which comes from the undeleted rows

  5. Restart JIRA

Cause 2 :

  1. Identify the problematic group_name and user_name.
  2. Run the following SQL Query on the JIRA Database:

    This will list the information of the group details for each directory.

  3. With the result from the above query, take note of the id and directory_id as it will be needed later.

  4. Next, Run the following SQL query against JIRA Database:

    The query will list down all of the membership under the problematic user_name.

  5. From the above result, compare the parent_id and directory_id of cwd_membership whether it have the same value as id and directory_id of cwd_group. If the value is exactly the same, this is not the issue.

  6. If the value of parent_id(cwd_membership) and id(cwd_group) have the same value but it is not reflecting the directory_id value this means it is mismapped.
    (info) Example: In table cwd_group the id = '10000' is tied to directory_id = '1', but in cwd_membership for that particular user the parent_id = '10000' is tied to directory_id = '2' where it should be '1'.

  7. Remove the problematic row(s) by executing this SQL query against JIRA database:

    (warning) The above command would delete all groups that have the mismapped directory_id.

  8. Restart JIRA.

 

 

 

Related Content

 Expand to see related content
Help us improve!
Is this article helpful?
Is the content complete?
Is it well written?

 

 

 

 

 

 

 

 

 

 

  • No labels

1 Comment

  1. We have just noticed that we have quite a few users in this state but we also noticed that the above SQL will delete nested group memberships:

    The correct delete statement would be