Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #6403
Closed
Open
Issue created Jun 23, 2025 by dockx thibault@tdockxDeveloper

[Orchestrator] - Some attributes could be fetched by orchestrator directly instead of being stored within FD Ldap - avoiding potential duplication

[Orchestrator] - Some attributes could be fetched by orchestrator directly instead of being stored within FD Ldap - avoiding potential duplication

For example, tasks extractor, conserves a multi-evaluated list of emails extracted from members. Orchestrator should only take the members in order to get the emails.

This is to be evaluated, analysed properly to see any potential impact on the creation and workflow of subtasks.

Assignee
Assign to
Time tracking