Issue Summary

Larger customers like Accenture have configured their Org-specific consent screen (shown at id.atlassian.com/login/consent during Jira Cloud login for Accenture users) But the same cannot be configured for Bitbucket Cloud

Steps to Reproduce

1. Use an Atlassian account on the Accenture domain (e.g., user@accenture.com).
2. Attempt to sign in to Jira Cloud.

Observe:

1. Redirect to id.atlassian.com/login/consent.
2. Display of the custom Accenture Privacy Notice consent screen.
3. Using the same type of account, attempt to sign in to Bitbucket Cloud (https://bitbucket.org).

Observe:
The custom consent pop-up is not consistently presented in the same way as in Jira (per customer report/expectation gap).

Expected Results

Ability to have the similar consent screen for the Bitbucket login too

Actual Results

No possibility for a similar consent screen during the Bitbucket login.

Reasons:

We do not currently provide any public APIs, extension points, or supported mechanisms in Bitbucket Cloud that allow such a mandatory pop-up.

Preliminary investigation indicates that extending our existing implementation is not possible because Bitbucket Cloud workspace URLs are not tenanted, so a different solution would need to be explored.

Workaround

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