BitBucket LDAP and Nested Groups Not Working

[FD Moore]

I'm trying to get LDAP AD nested groups to work for our Bitbucket Project Creator role but it's not working.  Users can logon, but they have no permissions to create projects.

I used this article as my guide, which says what I'm trying to do is possible (although the article is for Confluence):

https://confluence.atlassian.com/adminjiraserver072/managing-nested-groups-828787688.html

1.  We have a Domain Users group in AD with all users in the domain

2.  We have a Bitbucket-PO group also,  Domain Users is a group member of the Bitbucket-PO group.

3.  We have nested groups enabled

Our scenario is the exact same scenario as Example 2 in the article.

According to the article, a member of the Domain Users group will inherit permissions assigned to the Bitbucket-PO group.  But that is not working, we get the screen that only allows us to create personal projects.

However, if I add an AD account manually to the Bitbucket-PO group in AD, I get the permissions I need.  So it appears that it doesn't like nested AD groups but flat groups work fine.

Am I missing something? 

[Hitendra Chauhan]

Can you share the group and user filter you are using in Crowd ?

We are using several level of nesting in Active Directory and it works perfectly fine in Jira, Bitbucket and Confluence. So I am quiet sure that there is something to do with Group or user filter.