The Error "No Unique Capability has Been Found" Occurs while Editing Customer Permissions in a Service Project

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

When Editing Customer Permissions in a Service Project, then clicking "Save Change" , the error "No Unique Capability has been found" appears in the corner of the screen. In the browser's web console, you can see an HTTP 409 Response as well which indicates a conflict between the application server and database.

As a result, you cannot modify customer permissions in this project, such as changing the setting "Allow sharing with customer groups added to this project".

(Auto-migrated image: description temporarily unavailable)

Environment

5.12.5 +

Diagnosis

  • You are not able to update customer permissions in a service project

  • You see an HTTP 409 Error while trying to modify customer permissions in the project

  • You see the error "No Unique Capability has been found" appear after trying to save changes on the Customer Permissions page within the Service Project

Cause

There are duplicated "CAPABILITY_NAMES" in the table "AO_54307E_CAPABILITY"

You can check to confirm this by running the following SQL on Jira's Database:

1 2 3 4 5 6 7 8 9 10 11 -- TARGETING DUPLICATE DATA PER SERVICE_DESK_ID ON THE "AO_54307E_CAPABILITY" TABLE FOR POSTGRES SELECT "SERVICE_DESK_ID","CAPABILITY_NAME" FROM( SELECT "ID", "SERVICE_DESK_ID", "CAPABILITY_NAME" , row_number() OVER (PARTITION BY "SERVICE_DESK_ID","CAPABILITY_NAME" ORDER BY "CAPABILITY_NAME" ) FROM "AO_54307E_CAPABILITY" ) s WHERE s.row_number > 1;

If data returns, you are impacted by this issue and should proceed with the solution. Otherwise, please contact Atlassian Support for further investigation

Solution

To resolve this issue, Remove the duplicate "CAPABILITY_NAMES" in the table "AO_54307E_CAPABILITY"

⚠️ The query below is unsupported.

⚠️ Backup Jira's Database before running the delete statement

ℹ️ It is written for a Postgres Database and will require updates prior to running on other database types. Please use this at your own risk and discretion

1 2 3 4 5 6 7 8 9 10 11 -- DELETING DUPLICATED DATA DELETE FROM "AO_54307E_CAPABILITY" WHERE "ID" IN (SELECT "ID" FROM (SELECT "ID", "SERVICE_DESK_ID", "CAPABILITY_NAME", row_number() OVER (PARTITION BY "SERVICE_DESK_ID","CAPABILITY_NAME" ORDER BY "CAPABILITY_NAME" ) FROM "AO_54307E_CAPABILITY") s WHERE s.row_number > 1);
Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.