plugin_event issueshttps://gitlab.in2p3.fr/tev/plugin_event/-/issues2018-05-18T05:04:29+02:00https://gitlab.in2p3.fr/tev/plugin_event/-/issues/11Run several aggregation functions on the same database field in metric 1D2018-05-18T05:04:29+02:00LE GAC RenaudRun several aggregation functions on the same database field in metric 1D* In the current implementation, an internal error is raise when runnig a metric 1D using the column `min(history.data.age)` and `mean(history.data.age)` at the same time.
* It is is related to the use of the same database field with tw...* In the current implementation, an internal error is raise when runnig a metric 1D using the column `min(history.data.age)` and `mean(history.data.age)` at the same time.
* It is is related to the use of the same database field with two different aggregation functions.
* It might be interesting to remove this bottleneck.
* One user case can be found in `track_lhcbfrance` *metric1D / promotion per grade*. The idea is to display at the same time the min, mean and max age for a given grade.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/10Review code compliance with pylint and jslint.2018-05-18T05:04:29+02:00LE GAC RenaudReview code compliance with pylint and jslint.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/9Migrate the python documentation to sphynx2018-05-18T05:04:29+02:00LE GAC RenaudMigrate the python documentation to sphynxhttps://gitlab.in2p3.fr/tev/plugin_event/-/issues/8Sort list in decreasing order2018-05-18T05:04:29+02:00LE GAC RenaudSort list in decreasing order* List can be sort according to the value of several fields
* The sort order is always `ASC`
* Allow the `DES` using the web2py construct `~`, *i.e* `~year` or `~teams.team`, ....
* A user case is the list `track_lhcbfrance / promotio...* List can be sort according to the value of several fields
* The sort order is always `ASC`
* Allow the `DES` using the web2py construct `~`, *i.e* `~year` or `~teams.team`, ....
* A user case is the list `track_lhcbfrance / promotion CNRS` where promotion should be displayed in decreasing year.
https://gitlab.in2p3.fr/tev/plugin_event/-/issues/7Remove the constraint on the start date in reports2018-09-16T18:39:26+02:00LE GAC RenaudRemove the constraint on the start date in reports* Currently the `start date` has to be specified in list / metric reports.
* Remove this constraint.
* If not specified scan all database entries.* Currently the `start date` has to be specified in list / metric reports.
* Remove this constraint.
* If not specified scan all database entries.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/6Add the possibility to filter a list / metric on the field history.data2018-09-16T18:39:26+02:00LE GAC RenaudAdd the possibility to filter a list / metric on the field history.data* In list (metric) filter add the field data
* The filter operation is `contains`* In list (metric) filter add the field data
* The filter operation is `contains`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/5Add option to activate / de-activate the summary row in metric 2D2017-04-06T16:43:21+02:00LE GAC RenaudAdd option to activate / de-activate the summary row in metric 2D* The summary is miss leading in `track_lhcbfrance / dotation per year`
* The option has to be add in the metric configuration.* The summary is miss leading in `track_lhcbfrance / dotation per year`
* The option has to be add in the metric configuration.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/4Few bugs running track_lhcbfrance2016-01-07T17:52:32+01:00LE GAC RenaudFew bugs running track_lhcbfrance* [x] When running the metric 2D `age / nom /catégorie`, applying a filter on the `Qualité personne` failed with an `internal error`.
* [x] Summary information are wrong in `list/budget per line`* [x] When running the metric 2D `age / nom /catégorie`, applying a filter on the `Qualité personne` failed with an `internal error`.
* [x] Summary information are wrong in `list/budget per line`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/3Improve the branching model using GitLab functionalities2015-05-20T20:53:45+02:00LE GAC RenaudImprove the branching model using GitLab functionalities* In the commit 15dd10, the branching model described in http://nvie.com/posts/a-successful-git-branching-model have been adopted. It relies on the branches: master, develop, feature, hotfix and release.
* Later on, the git repository ...* In the commit 15dd10, the branching model described in http://nvie.com/posts/a-successful-git-branching-model have been adopted. It relies on the branches: master, develop, feature, hotfix and release.
* Later on, the git repository has been migrated to GitLab.
* The branching model can be simplified using the GitLab functionalities **issues tracking** and **merge request** as recommended in http://doc.gitlab.com/ee/workflow/gitlab_flow.html.
* The branching model is based on two stable branches **master** and **production**.
* Each code modification (bug fix, improvement, ...) start with an issue.
* For each issue a feature branch is created. Its name starts with the issue number.
* When the code for the issue is finished, it is pushed in the master branch via a *merge request*. The merge request description has to contains the issues number (fixes #14, closes #67, etc.). The issue has to be closed and the branch has to be deleted when the merge request is accepted.
* When the master branch reach a point corresponding to a release, it is pushed in the production branch via a *merge request*.
* An *hot fix* start by an issue. It is prepared in a dedicated branch. Once ready the dedicated branch is push to the master via a *merge request* (conflict might be solved at that time). The hot fix branch is pushed to the production branch when the hot fix is working in the master branch. Then the hot fix branch is deleted.
* The script ``buildVersion.py`` as to be renamed ``build_version.py`` and adapt to the branching model
* The branch `production` has to be created from the master branch at b7e3c8.
* The branch `develop` has to be merge in the master branch via a merge request.
https://gitlab.in2p3.fr/tev/plugin_event/-/issues/2duplicate entries in the history table of the track_teams application2015-05-18T20:22:04+02:00LE GAC Renaudduplicate entries in the history table of the track_teams application* The history table contains many duplicate entries after the migration of the track_teams to the track_events paradigm.
* This is true for the test as well as for the prodution database. * The history table contains many duplicate entries after the migration of the track_teams to the track_events paradigm.
* This is true for the test as well as for the prodution database. https://gitlab.in2p3.fr/tev/plugin_event/-/issues/1Rename database fields2018-05-18T05:04:30+02:00LE GAC RenaudRename database fields* In order to keep consistency with the others data table and to avoid ambiguities, rename the database fields in the following ways:
```
objects.reference --> objects.object
objects.serial_number --> objects.reference
obj...* In order to keep consistency with the others data table and to avoid ambiguities, rename the database fields in the following ways:
```
objects.reference --> objects.object
objects.serial_number --> objects.reference
objects.batch_number (decide to keep it or not)
events.data --> events.model (to avoid confusion with history.data)
```