Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30846

Sibling and parent Nested Groups ignored when resolving members

XMLWordPrintable

    • 5.01
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 November 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 06 November 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

      We have a company with multiple users and many security group in our Active Directory.

      For clarity, we have separated our Jira Groups in our Active Directory
      org/atlassian/3rdParties/Jira/

      Users are crawled from the domain root, therefor
      org/atlassian/
      And the group use the sub-path 3rdParties/Jira

      Various management groups can be found under the root
      org/atlassian/Office1/Developers/
      org/atlassian/Office2/Marketing/

      If a nested group refer to a group that is not under org/atlassian/3rdParties/Jira/ it is ignored

      For instance, if we want to add a group in Jira, jira-developers, that has
      org/atlassian/Office1/Developers/all-developers as a member, this will be ignored.
      On the other hand, if org/atlassian/3rdParties/Jira/myTestGroup is added, it will be added.

      This restriction render nested group unusable on organized Directory where group are isolated per function or physical location. Nested group should be able to follow any member group no matter where it is located in the active directory.

              Unassigned Unassigned
              49380b3a1ecf Philippe Busque
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: