Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug of display when moving in the chronology (date not correctly taken into account #1813

Closed
manonviallet opened this issue Jan 11, 2022 · 0 comments
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@manonviallet
Copy link
Contributor

Description

In the knowledge part of a report, when moving along the chronology, it seems that only the start date is taken into account for some relations, and not the duration.

As an example as shown in the picture below, I have a report with a relation spanning from beginning 2017 to 2020. However, when I move the cursor along the timeline, the relation inexplicably disappear around 2017-07.

Capture d’écran du 2022-01-11 18-15-00

Capture d’écran du 2022-01-11 18-15-00

Environment

Demo 5.1.3

Expected Output

Have the relation displayed for its entire period of duration

@manonviallet manonviallet added the bug use for describing something not working as expected label Jan 11, 2022
@SamuelHassine SamuelHassine added this to the Release 5.2.0 milestone Feb 1, 2022
@SamuelHassine SamuelHassine added feature use for describing a new feature to develop and removed bug use for describing something not working as expected labels Mar 21, 2022
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Sep 29, 2022
@SamuelHassine SamuelHassine removed this from the Release 5.4.0 milestone Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants