Issue Summary

• As per this issue description, after transferring a repository that already has Pipelines enabled to a new workspace, Pipelines will be automatically disabled and the user that performed the transfer will not be able to enable Pipelines back;

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. Transfer a repository that has Pipelines enabled to a new workspace;
2. Once the repository is transferred, you will find the following banner inside the Pipelines menu:
   

Expected Results

1. The user who transferred the repository should be able to re-enable Pipelines

Actual Results

1. If the user who transferred the repository clicks on the banner to go to settings, they will be faced with a 404 error;
2. If they go to the settings directly, the Pipelines section will be missing;
3. It is also not possible to re-enable Pipelines through the API:

   $ curl -X PUT \
   --header 'Accept: application/json' \
   --header 'Content-Type: application/json' \
   --url "https://api.bitbucket.org/2.0/repositories/<workspace>/<repository>/pipelines_config" \
   -d '{"enabled": true}'
   {
     "error": {
       "message": "Not found",
       "detail": "Account {<uuid>} does not exist.",
       "data": {
         "key": "account-service.account.not-found",
         "arguments": {
           "uuid": "{<uuid>}"
         }
       }
     }
   }
   

Workaround

• This issue seems to be affecting only users who were already part of the workspace prior to the transfer;
• In order to work around this issue, a new user with admin privileges must be added to that repository and will need to click on the banner to be re-directed to the Pipelines settings and enable Pipelines once again;
• After this new user enables Pipelines, the original user should be able to see the Pipelines settings once again;