Deleting a Label with Identical Name and Prefix Causes API Error for Subsequent Creator

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • Component/s: Organize - Labels
    • None
    • Minor

      Issue Summary

      When multiple users create labels with the same prefix and name in Confluence, each label is assigned a unique ID. However, if a user attempts to delete a label that they created after another user has created an identical one, the API returns an error. This issue occurs despite the labels having distinct IDs, and only the user who first created the label with that prefix and name can successfully delete it. This behavior restricts subsequent creators from managing their own labels independently.

      Steps to Reproduce

      1. User A creates a label to a Confluence content, with a prefix and name using https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-labels/#api-wiki-rest-api-content-id-label-post 
      2. User B creates a label to the same Confluence content, with the same prefix and same name, using https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-labels/#api-wiki-rest-api-content-id-label-post 
      3. User B tries to delete it, using https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-labels/#api-wiki-rest-api-content-id-label-label-delete or https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-content-labels/#api-wiki-rest-api-content-id-label-delete 

      Expected Results

      User B should be able to delete it, since that user created it

      Actual Results

      Error 403

      {
         "statusCode": 403,
         "data": {
            "authorized": false,
            "valid": true,
            "errors": [],
            "successful": false
         },
         "message": "com.atlassian.confluence.api.service.excpetions.PermissionExcepetion: Could not delete label from content with id ContentId{Id=<contentID>}"
      }

       

       

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Emile Givental
            Reporter:
            Emmanuel Bellezza
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: