Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
stork
stork
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 152
    • Issues 152
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #331

Closed
Open
Opened Jun 26, 2020 by Marcin Siodelski@marcinMaintainer

Issues with initial fetch of user groups

When I was reviewing #310 (closed) I found that system groups are not properly fetched by the UI. When I entered the users view, the drop down that normally allows for selecting which group the new user should belong to was empty. Also, the non admin user had 'unknown' group assigned in the users list. It seems there was a race between services in getting the list of groups.

The viable solution seems to be to move the initialization of the groups to the ServerDataService.

Assignee
Assign to
0.9
Milestone
0.9 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/stork#331