Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S slapos.core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slapos.core
  • Merge requests
  • !640

Merged
Created Jun 05, 2024 by Romain Courteaud@romain🐙Owner

Subscription change request

  • Overview 2
  • Commits 6
  • Changes 72

Like a Subscription Request, a Subscription Change Request is used to create a new Open Sale Order, but, it also archive a previous one at the same time.

The purpose is to change some parameters of an Open Sale Order, and correctly created compensation movement, to ensure the resource stock is correct.

Stop using discount resource, and reduce the quantity of the consumed software product / service

Only Sale people can create Subscription Change Request.

TODO: check how quantity precision can be defined

The only use case supported for now is changing an Instance Tree's user.

Edited Jun 06, 2024 by Romain Courteaud
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: subscription_change_request
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7