Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-21

Some Atlas users are not able to add contributors to a project unless they become a "trusted user" role

XMLWordPrintable

    • Minor

      Issue Summary

      There are some Atlassian Accounts that do not see the dropdown of users when trying to add contributors to a project. The user can be a product admin or product user. The user can see their teams in the Teams part of Atlas but they cannot add users.

      Steps to Reproduce

      1. Have an affected Atlassian Account
      2. Go to a project
      3. Try and Add a contributor to that project. 

      Expected Results

      Any person using Atlas should be able to add contributors to a project 

      Actual Results

      Some users get an empty list when trying to add a contributor to a project

      Workaround

      The workaround for these users is to make them a trusted user in your Atlassian Site. 

            [ATLAS-21] Some Atlas users are not able to add contributors to a project unless they become a "trusted user" role

            Leon van Tuijl added a comment - - edited

            Also the same behavior for my company. We have a free license for atlas and a paid license for jira/confluence and all users are 'managed users' through DNS domain verification. I did some tests and my conclusion is that. Only users that also are part of a paid license can add or even see the followers/contributors/owner in any dropdown in (free) Atlas.

            I hope this is not intended functionality. Atlassian products are mainly used right now for the IT department. We are running some trails with other departments to also add their projects to Atlas but then we encountered this issue because they don't use Jira/confluence.

            Leon van Tuijl added a comment - - edited Also the same behavior for my company. We have a free license for atlas and a paid license for jira/confluence and all users are 'managed users' through DNS domain verification. I did some tests and my conclusion is that. Only users that also are part of a paid license can add or even see the followers/contributors/owner in any dropdown in (free) Atlas. I hope this is not intended functionality. Atlassian products are mainly used right now for the IT department. We are running some trails with other departments to also add their projects to Atlas but then we encountered this issue because they don't use Jira/confluence.

            Adam Ploof added a comment - - edited

            We are experiencing the same behavior with our non-managed users (i.e. users without product access to Atlassian products that we pay for). The trusted role has been discontinued but the issue remains effectively unchanged.

            For more background on our setup:

            • We sync our Atlassian directory with our identity provider
            • Our access policy for Atlas is: invites are allowed for our domain but require admin approval

            The expected behavior in our case would be that Atlas users who do not have access to other Atlassian products that we pay for (e.g. JSM) should still be able to view a list of users in our directory when adding to contributors/sharing/etc. For example, this is how JSM works when a customer-only user adds a request participant.

            Adam Ploof added a comment - - edited We are experiencing the same behavior with our non-managed users (i.e. users without product access to Atlassian products that we pay for). The trusted role has been discontinued but the issue remains effectively unchanged. For more background on our setup: We sync our Atlassian directory with our identity provider Our access policy for Atlas is: invites are allowed for our domain but require admin approval The expected behavior in our case would be that Atlas users who do not have access to other Atlassian products that we pay for (e.g. JSM) should still be able to view a list of users in our directory when adding to contributors/sharing/etc. For example, this is how JSM works when a customer-only user adds a request participant.
            Yerbol Nisanbayev (Inactive) made changes -
            Assignee Original: Damon Cai [ 0bb2ae2c1cc3 ] New: Kavi Lal [ 9c53f706aadb ]
            Damon Cai made changes -
            Status Original: Needs Triage [ 10030 ] New: Long Term Backlog [ 12073 ]
            Damon Cai made changes -
            Assignee Original: Aditya Karia [ akaria@atlassian.com ] New: Damon Cai [ 0bb2ae2c1cc3 ]
            Jesse Klein created issue -

              9c53f706aadb Kavi Lal
              jklein@atlassian.com Jesse Klein
              Affected customers:
              8 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: