Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 149
    • Merge requests 149
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !2227

Open
Created Jan 09, 2026 by Rafael Monnerat@rafael👓Owner
  • Report abuse
Report abuse

Draft: Use destination_decision for Assignment request to prevent conflict

  • Overview 1
  • Commits 1
  • Changes 7

Assignments use destination to set Organisation, due to this, we switch to use destination_decision instead, as a way to link Assignment Request to the Person.

This allows use Assignment Requests to update Organisation's on projects that relies on it to set security.

Destination Decision is not used on Assignments, so it is future safe and will not conflict with future extensions of Assignment Requests and/or Assignments implementation.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: assignment-request-fixup
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7