Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

Wrong evaluation timeframe displayed when switching evaluations #2585

Closed
jetzlstorfer opened this issue Oct 23, 2020 · 3 comments · Fixed by #2665
Closed

Wrong evaluation timeframe displayed when switching evaluations #2585

jetzlstorfer opened this issue Oct 23, 2020 · 3 comments · Fixed by #2665
Assignees
Labels
bridge:evaluation bridge.2.0 Bridge Version 2 type:bug Something is not working as intended/documented
Milestone

Comments

@jetzlstorfer
Copy link
Member

In the evaluation screen in the bridge, when switching from one evaluation to another, the timeframe is not calculated correctly. It seems that the initial timeframe is stuck and not replaced with the timeframe of the clicked evaluation event.

In the example, the timeframe of the preselected event is 5 minutes and it doesn't change, no matter which event is clicked.

image

image

image

@jetzlstorfer jetzlstorfer added type:bug Something is not working as intended/documented bridge.2.0 Bridge Version 2 bridge:evaluation labels Oct 23, 2020
@johannes-b johannes-b added this to the 0.7.3 milestone Oct 27, 2020
@johannes-b johannes-b added the next-sprint Items that should be discussed and implemented in the next sprint label Oct 27, 2020
@Godtide
Copy link
Contributor

Godtide commented Oct 31, 2020

Assign to me

@johannes-b johannes-b removed the next-sprint Items that should be discussed and implemented in the next sprint label Nov 2, 2020
@christian-kreuzberger-dtx
Copy link
Member

Hi @Godtide , can you give us an ETA when this is ready?

@ermin-muratovic
Copy link
Member

@Godtide as discussed last thursday in our community meeting, I'll take this issue, since we need it for our 0.7.3 release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bridge:evaluation bridge.2.0 Bridge Version 2 type:bug Something is not working as intended/documented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants