Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • N notifications-routing
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Notifications project
  • notifications-routing
  • Issues
  • #37
Closed
Open
Issue created Mar 05, 2021 by Carina Antunes@crdeolivOwner

Bugfix: Channel's user list

Fix channels's user list generation: currently we're not validating if a user coming from grappa already has an account on our platform.

Proposed solution:

  • After getting users from grappa, if the user is not already is the channel users list, try fetching the user from our db by username. Consider performance implications of fetch in bulk of one by one.

A couple of specs:

  • If user exists in both grappa and db we need to give priority to data from users coming our db
Edited Mar 05, 2021 by Carina Antunes
Assignee
Assign to
Time tracking