Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
fusiondirectory-plugins
fusiondirectory-plugins
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • 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
  • fusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #5943

Closed
Open
Opened Apr 05, 2019 by agallavardin@agallavardinReporter

SINAPS : if contact method are not the same or missing in sinaps , acquisition must be sent

Requirements

Descriptive title for this enhancement

when diffusion is done, contact method must be compared, if there are different or not exist on SINAPS, acquisition must be done

Actual behavior

no acquisition is done after diffusion

Expected behavior

when diffusion is done, contact method must be compared, if there are different or not exist on SINAPS, acquisition must be done

Step by step description of new behaviour

  1. diffusion is done to Fusion
  2. compare contact method from sinaps and Fusion , if different ( incorrect or missing on sinaps side) an acquisition is mandatory
  3. lanch acquisition if necesary

Benefits

coherence between SINAPS an FD

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: fusiondirectory/fd-plugins#5943