Open issues

Order by Priority
  1. Suggestion
    BSERV-5108Synchronize User directory using REST API
  2. Suggestion
    BSERV-7558Automate LDAP configurations in multiple instances
  3. Suggestion
    BSERV-20159To include "x-hub-signature" header in Webhook Test Connection payload when using secret token
  4. Suggestion
    BSERV-20158Support for Elasticsearch 7.17.19
  5. Suggestion
    BSERV-5195Add ability to Migrate Users from one directory to another
  6. Suggestion
    BSERV-13081Jira Cloud integration does not show old commit details
  7. Suggestion
    BSERV-13576Provide an API endpoint for Advanced Repository Management
  8. Suggestion
    BSERV-13709Enable authentication using HTTP Access Tokens while username/password auth is disablec
  9. Suggestion
    BSERV-20155Bitbucket Data Center support for newer versions of amazon open search.
  10. Suggestion
    BSERV-20156Add a webhook trigger for repository created events
  11. Suggestion
    BSERV-2596Show number of changed/added/deleted lines in commit/PR view
  12. Suggestion
    BSERV-5384Ability to render other README formats, such as reStructuredText
  13. Suggestion
    BSERV-11329Allow individual users to toggle PR email notifications by event
  14. Suggestion
    BSERV-12217Please add the option to override project Default Reviewers settings at the Repository Level
  15. Suggestion
    BSERV-14533CSP Support for Bitbucket Server
  16. Suggestion
    BSERV-19802Option to disable the "Can't log in?" link on the login screen
  17. Suggestion
    BSERV-20157Remove permissions from personal repositories of deleted users
  18. Suggestion
    BSERV-9560Document how to set heap size for Elastic Search process
  19. Suggestion
    BSERV-12949Increase git commit message cell length
  20. Suggestion
    BSERV-10631Ability to add more fields in the development panel.
  21. Suggestion
    BSERV-3055Add setting in Stash Administration to disable changing project keys and project names
  22. Suggestion
    BSERV-3683Language aware code navigation
  23. Suggestion
    BSERV-4929Pull request REST API: Find by author, reviewer, date range, content
  24. Suggestion
    BSERV-7858JIRA trigger to transition issue as soon as the LAST open pull request is merged
  25. Suggestion
    BSERV-13247Add support for Elasticsearch 8
  26. Suggestion
    BSERV-13538Prevent secrets from getting into repositories
  27. Suggestion
    BSERV-18983Secret Scanning - Perform Re-Scan on add/update of Rules
  28. Suggestion
    BSERV-2468Add paths to project/repo structure
  29. Suggestion
    BSERV-2628Code snippet sharing
  30. Suggestion
    BSERV-2727Allow projects to be categorised
  31. Suggestion
    BSERV-3035Add support for integrated authentication for Microsoft SQL Server
  32. Suggestion
    BSERV-3203Automatically or Manually remove Running builds from Pull Requests if build is missed
  33. Suggestion
    BSERV-5513Improve branch-utils REST API documentation to clarify what information is returned about branches
  34. Suggestion
    BSERV-7277Add support for GlusterFS in Bitbucket Data Center
  35. Suggestion
    BSERV-7667Date & time format options, or localisation
  36. Suggestion
    BSERV-10028Ability to remove Project Default Permission
  37. Suggestion
    BSERV-12681Restrict Admin from adding some groups to repository and project permissions
  38. Suggestion
    BSERV-13542Adding LDAP groups to Default reviewers in Project/Repo settings
  39. Suggestion
    BSERV-19046DC Certification for Permission Lockdown Plugin
  40. Suggestion
    BSERV-19627Set the Mesh access log level to ERROR by default
  41. Suggestion
    BSERV-19729Enhance Logging for Duplicate Pull Request Detection
  42. Suggestion
    BSERV-13301Mesh: customize the replication factor for individual repositories
  43. Suggestion
    BSERV-20102Allow Usage of Atlassian’s Remote Model Context Protocol (MCP) with Bitbucket Data Center
  44. Suggestion
    BSERV-4142Ability to filter and bulk delete merged or stale branches
  45. Suggestion
    BSERV-8765Limit project admin ability to grant additional permissions
  46. Suggestion
    BSERV-10230Allow to omit redirection feature when renaming a repostiory
  47. Suggestion
    BSERV-12496Rate limit for git operations
  48. Suggestion
    BSERV-13159Adding reviewer group to default reviewers
  49. Suggestion
    BSERV-2852Cross repository activity stream
  50. Suggestion
    BSERV-3051Ability to rename groups
Refresh results
1 of 2333
Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-5108

Synchronize User directory using REST API

    • 45
    • 22
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We have Crowd and stash users/group is managed in Crowd server. We have setup 60 min as synchronization interval to get the updated password and users from Crowd. This is OK and working fine, some users need the password update as soon it is done in crowd.
      Is there any way I can automate the synchronize from crowd -> Stash using a REST call , so that users can run after they change the password in crowd.

            No work has yet been logged on this issue.

              Unassigned Unassigned
              dlee@atlassian.com Deric Lee (Inactive)
              Votes:
              68 Vote for this issue
              Watchers:
              46 Start watching this issue

                Created:
                Updated: