Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5437

Indicate in JSD when customer is in Crowd and has no permission to authenticate

XMLWordPrintable

    • 1
    • 2
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Current Behavior:

      JIRA can be connected to Crowd and customers may appear in the Crowd directory. Crowd allows the admin to select from the following:

      • Allow all to authenticate
      • Allow only members of configured groups to authenticate

      Regardless of the selection all users in the directory will appear in JIRA's list of users. When JSD is set to allow anyone with an account these users will also appear in the customer list on JSD projects.

      Can cause problems for JSD admins when this is set to allow only configured groups.

      • Users who appear in the customer lists are believed to be able to log into the customer portal.
      • In reality these users are not able to log in because they do not have permission to authenticate in Crowd.
      • JSD Admin does not expect that these users need to be added to any group. Does not see any indication that the users are unable to log in.

      Suggested Change
      Add indicator to customer list that will show if a user is not able to authenticate.

            [JSDSERVER-5437] Indicate in JSD when customer is in Crowd and has no permission to authenticate

            Charlie Marriott added a comment -
            Atlassian Update – 27 Jan 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 27 Jan 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: