Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-orchestrator fusiondirectory-orchestrator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-orchestratorfusiondirectory-orchestrator
  • Issues
  • #62
Closed
Open
Issue created Nov 07, 2024 by dockx thibault@tdockxMaintainer

[Orchestrator] - lifeCycle prolongation adds time from date of process and not from resource end date

[Orchestrator] - lifeCycle prolongation adds time from date of process and not from resource end date

Any prolongation should potentially start from the previous resource end date. Any start date should be the end of the previous resource.

If no previous resource set, it should either be set during account creation or set as the date of processing.

Assignee
Assign to
Time tracking