Why nesting of internal groups does not work for AD users?

[Gregory Kneller]

Here is scenario:

There are 2 directories in JIRA (v. 6.2.7):  first is internal and another is from AD (with option "Read Only, with Local Groups", nesting is enabled)

There are two users: INT (in internal dir)  and AD (from active-directory/LDAP dir), 

and two groups, defined in JIRA: A and AA (AA is nested into A).

Both users INT and AD are members of  AA group.

In JIRA instance, user INT is attributed to A group (as expected) , but user AD is NOT in A group (that is strange). I.e, group A is not shown in group list for  AD user at Users page, and JIRA does not recognize AD as a member of A group in schemes, projects, etc.

In Confluence instance, that uses JIRA as directory provider, both INT and AD users attributed to A group as well as to AA.

Why does it work this way and how to make it working as expected? (Both AD and IND users shall be attributed to A group in JIRA)?

[Gregory Kneller · Accepted solution]

This is due to  https://jira.atlassian.com/browse/JRA-24671

[Henning Karl]

We also have exactly the same problem that nesting of internal groups does not work for AD users.

Gives a workaround for this issue?