Feat REST: allow Account ID to be used to update users in branch-restrictions

[Sander Mol]

The current endpoint of https://api.bitbucket.org/2.0/repositories/<username>/<repository>/branch-restrictions does not allow for users to be posted by "account_id". Currently, only "username" and "uuid" is supported.

I would expect the following post body to be supported

{
   "type": "branchrestriction",
   "kind": "restrict_merges",
   "value": null,
   "branch_match_kind": "branching_model",
   "branch_type": "development",
   "users": [{
      "account_id": "<account_id>"
   }]
}

This currently results in a successful post, but without a user actually being posted. This is especially relevant now that Account ID is used in more and more places as the preferred identification field.

Related:

https://community.atlassian.com/t5/Bitbucket-questions/Feat-Swagger-V3-Update-account-schema/qaq-p/2694518

[Theodora Boudale · Accepted solution]

Hi Sander,

Thank you for the feedback. I went ahead and created a request in our issue tracker:

• https://jira.atlassian.com/browse/BCLOUD-23240

You can vote for it (by selecting the Vote for this issue link) and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Implementation of features is done as per our policy here and any updates will be posted in the feature request.

Kind regards,
Theodora

[Sander Mol]

Thank you very much for creating this issue!

[Theodora Boudale]

You are very welcome! Please feel free to reach out if you ever need anything else!