User added to group in crowd is not visible in JIRA group view

XMLWordPrintable

    • 4
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 16 November 2017

      Hi everyone,

      The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low.
      Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out.

      Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

      Cheers,
      Ignat Alexeyenko
      Jira bugmaster.

      Show
      Atlassian Update – 16 November 2017 Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

      The instance of JIRA use crowd (2.0.3) for user management.
      In JIRA the following property is on: External user management
      In Jira a member of the jira-user group has the right to create an issue

      Steps done:
      In crowd:
      1) create user
      2) add user to group jira-user

      In Jira
      1) log in as the new user -> no right to create an issue
      2) log in as an administrator
      3) in "user browser" screen search for the new user -> he exists and he is in group "jira-user"
      4) click on jira-user group -> the user is not part of the list of users ????

      So from the user view we see that the user is member of "jira-user" but in group view the user is not member.

      I had to restart jira for him to be "full" member, I did not wait for cache expiration.

              Assignee:
              Unassigned
              Reporter:
              Doe
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: