Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • P plugin_event
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Now running Gitlab v15.9.3. More info.

  • tev
  • plugin_event
  • Issues
  • #21
Closed
Open
Issue created Jan 13, 2017 by LE GAC Renaud@legacOwner

Fix the event identifier in the EvtSelector

  • In order to compute properly if a person start / end in the given period, the method _active_period have been introduce in the EvtSelector .
  • The method determines the start (end) date(s) for person associated to an event, to a domain and to a team. The algorithm concatenate the different steps in which parameters like fte can change.
  • In the current implementation the event identifier is force to People.
  • This wrong since the selector can be applied to many different event. In addition, it should not depends on the application.
  • In order to fix it, the event identifier has to be extract from the configuration of the list or metrics.
  • One can imagine to modify the database schema for list and metric adding a field id_event
Assignee
Assign to
Time tracking