Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    BCLOUD-23749Adding a user to the workspace or repository should send an email to administrators
  2. Suggestion
    BCLOUD-20385Add the possibility to have per account billing instead of per workspace billing
  3. Suggestion
    BCLOUD-12947Customer request - Bulk-transfer repositories between workspaces.
  4. Suggestion
    BCLOUD-13176Make Audit Log info available via the API
  5. Suggestion
    BCLOUD-21867Convert Personal Workspace to Team Workspace
  6. Suggestion
    BCLOUD-22039Pipelines Build Usage across an entire workspace grouped by repositories
  7. Suggestion
    BCLOUD-22052Add in the Audit log the actor that invited the user
  8. Suggestion
    BCLOUD-22844Use previously downloaded Pipe image
  9. Suggestion
    BCLOUD-23106Autoscaler throwing FileNotFoundExceptions error
  10. Suggestion
    BCLOUD-23727Enable Default Variables During Preparsing in Bitbucket Pipelines
  11. Suggestion
    BCLOUD-23742Shared Volume between Pipeline Steps
  12. Suggestion
    BCLOUD-23744Wikis are accessible in all Bitbucket workspaces
  13. Suggestion
    BCLOUD-23746Shadow IT control for Bitbucket for Atlassian Organisations using the Original User Management
  14. Suggestion
    BCLOUD-23747Enhanced YML Validation for Bitbucket Cloud Pipelines
  15. Suggestion
    BCLOUD-23521Allow disabling of additional security measures for accounts without 2SV enabled.
  16. Bug
    BCLOUD-19689API and Git operations made within Pipelines build is blocked by IP whitelisting
  17. Suggestion
    BCLOUD-23748MCP server for Bitbucket cloud
  18. Suggestion
    BCLOUD-21994Support Application Tunnel for Bitbucket cloud
  19. Suggestion
    BCLOUD-23443Optimize size of react js webpack files to improve snippet creation speed
  20. Suggestion
    BCLOUD-20833Skip steps based on condition - Include SKIP and RUN on manual steps
  21. Suggestion
    BCLOUD-23410Add support for custom merge check trigger based on Jira
  22. Suggestion
    BCLOUD-13637Pipelines usage and build minutes report
  23. Suggestion
    BCLOUD-16304queuing and automatic resuming of paused deployment steps
  24. Suggestion
    BCLOUD-23741Add an option to change the default branching model
  25. Suggestion
    BCLOUD-23743Add file filtering to PR's
  26. Suggestion
    BCLOUD-23272Default landing page for pull requests
  27. Suggestion
    BCLOUD-23649Provide option to control Pipeline builds in Draft Pull Request.
  28. Suggestion
    BCLOUD-23256Not all pipeline builds shown against a commit/pull request only latest run is displayed
  29. Suggestion
    BCLOUD-20358Email notification for pipeline successful builds
  30. Suggestion
    BCLOUD-21695Trigger a pipeline only when a reviewer approves a pull request
  31. Suggestion
    BCLOUD-23212Require reviews/merge-checks by code owners
  32. Suggestion
    BCLOUD-23511GPG key for email alias
  33. Suggestion
    BCLOUD-23262Provide an option to monitor the parallel step limit usage in Bitbucket Cloud
  34. Suggestion
    BCLOUD-14346Include "last access" or "last login" dates in audit log along with entry when user was added to the Repository access
  35. Suggestion
    BCLOUD-20644JIRA Integration: Check for issue validity before linking issues
  36. Suggestion
    BCLOUD-20342Admin added to a personal workspace is unable to view the "Apps & Features", and "OAuth" options in the workspace settings
  37. Suggestion
    BCLOUD-23738Remote Model Context Protocol (MCP) Server for Bitbucket Cloud
  38. Suggestion
    BCLOUD-23740Provide an option to only send Slack notifications for 'Ready' pull requests
  39. Suggestion
    BCLOUD-23640Remove the display of Draft Pull Requests as the default option from the Pull Requests list.
  40. Suggestion
    BCLOUD-8586Support task lists in Markdown (BB-9699)
  41. Suggestion
    BCLOUD-22262Hide Sync Now link
  42. Suggestion
    BCLOUD-15191Configurable expiry for dependency caches to support builds with different dependencies
  43. Suggestion
    BCLOUD-21396Local cache/artifacts for Self-hosted Pipelines Runner
  44. Suggestion
    BCLOUD-21998Improve the experience of two-step verification in Bitbucket Cloud (2SV/2FA)
  45. Suggestion
    BCLOUD-23737Ability for Workspace-level SSH Keys with Signed Commits
  46. Suggestion
    BCLOUD-20175Import Repository Variables
  47. Suggestion
    BCLOUD-13931Add the ability to track number of API requests for hitting throttling limit purposes
  48. Suggestion
    BCLOUD-23232Customise Bitbucket Cloud notification email headers
  49. Suggestion
    BCLOUD-10471Git server-side "pre-receive" hook (BB-11418)
  50. Suggestion
    BCLOUD-10170Add pre-commit hook support to validate commits message format, rejects commits if validation fails
Refresh results
1 2 3 4 5Next >>
1 of 1548
Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-23749

Adding a user to the workspace or repository should send an email to administrators

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Product - Notifications
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Currently, there is no automated alert system to notify administrators or stakeholders when a new user is added to a workspace or repository. This lack of notification can lead to security and management challenges, as unauthorized or unexpected additions might go unnoticed.

      Steps to Reproduce

      1. Invite a user to the repository or workspace

      Expected Results

      An email should be sent to designated administrators or stakeholders, notifying them of the new user addition, including details such as the user’s name, email, role, and the specific workspace or repository they have been added to.

      Actual Results

      No alert or notification is sent when a new user is added to the workspace or repository. Administrators have to manually check the user lists to ensure all additions are authorized.

      Workaround

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

          Form Name

            • All
            • Comments
            • Work Log
            • History
            • Activity

              Unassigned Unassigned
              ncsupka Norbert Csupka
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                52 minutes ago
                Updated:
                44 minutes ago
                • Atlassian Jira Project Management Software
                • About Jira
                • Report a problem
                • Privacy policy
                • Notice at Collection

                Atlassian