Board administrators in Jira Software Data Center are unable to configure the board
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Certain Jira users (who are not Jira administrators) cannot configure a board even though they are present in the list of board administrators.
Environment
Jira Software Data Center 8.x and above.
Diagnosis
The following SQL queries can be used to find which board administrators (either users or groups) are affected by this problem:
Users
1
2
3
4
SELECT lower_user_name,"NAME" FROM "AO_60DB71_BOARDADMINS"
INNER JOIN app_user ON "AO_60DB71_BOARDADMINS"."KEY"=app_user.user_key
INNER JOIN "AO_60DB71_RAPIDVIEW" ON "AO_60DB71_BOARDADMINS"."RAPID_VIEW_ID" = "AO_60DB71_RAPIDVIEW"."ID"
WHERE "TYPE"='GROUP' AND lower_user_name NOT IN (SELECT group_name FROM cwd_group);Groups
1
2
3
4
SELECT group_name,"NAME" FROM "AO_60DB71_BOARDADMINS"
INNER JOIN cwd_group ON "AO_60DB71_BOARDADMINS"."KEY"=cwd_group.group_name
INNER JOIN "AO_60DB71_RAPIDVIEW" ON "AO_60DB71_BOARDADMINS"."RAPID_VIEW_ID" = "AO_60DB71_RAPIDVIEW"."ID"
WHERE "TYPE"='USER' AND group_name NOT IN (SELECT user_key FROM app_user);Cause
Jira stores the list of board administrators with a TYPE field that indicates whether the administrator is a user or a group. If the TYPE field becomes mismatched due to an incorrect manual database edit or any other kind of database corruption, the user or group will appear as normal in the Jira user interface's list of board administrators, but they will not be able to configure the board.
This does not apply to users who are also Jira administrators, since Jira administrator permissions are checked separately.
Solution
Remove the user or group from the list of board administrators and add them back again.
Was this helpful?