0.20 launch, UI display weird behaviours list

[ReLoutre]

Describe the issue

Here's a quick listing of the weird UI behaviour i came across in the newly launched 0.20 of Kestra, some points may be more of a "request and feedback" type, apologies.

---

Tasks

Beta Give feedback

1. As you can see with the two pictures above, the date filtering doesn't follow the date format specified in the settings. (Done in chore(ui): respect date format form setting inside filter label #6335)

---

---

Tasks

Beta Give feedback

1. As you can see with the above picture, some of the total executions legends (related to the gauge display) are out of bounding. (done in Align the pie chart labels when there are many states to display #5578 #5971)

---

---

Tasks

Beta Give feedback

1. As you can see with the above two pictures, hovering the filter box trigger the scrollbar which hide the majority of the filter himself, interacting with the filter is a lot more complicated. Moved to a separate issue : UI - Filter scroll bar behaviour is inconsistent #6338

---

---

Tasks

Beta Give feedback

1. As you can see with the above picture, green blocks, the field "next execution date" display a date for realTime triggers, which is weird, and what's more, it display instead the "creation date" i guess. Moved to a separate issue : UI - Triggers page, real TimeTrigger info display is weird #6340
2. As you can see with the above picture, red block, IDs of triggers are truncated, in my opinion this info is of upmost importance since it permits to understand easily the diff between triggers of the same flow. (Done in chore(ui): prevent wrap of trigger id columns #6336)

Environment

• Kestra Version: 0.20.0 OSS docker compose debian

[Muppasanipraneeth]

@MilosPaunovic can you assign it to me

[MilosPaunovic]

Yup, go ahead! 🚀

[Muppasanipraneeth]

sorry @MilosPaunovic sir I though it is reactjs but it is vuejs I am not familiar with it

[ReLoutre]

Found out that expanding then collapsing some of the right side menus fix the display of the executions legends.

[sanjaykumar584]

@MilosPaunovic I would like to work on this issue. Can you assign it to me?

[MilosPaunovic]

Absolutely, go for it @sanjaykumar584! 🚀

[MilosPaunovic]

Hey @ReLoutre,

First two issues from the list are amended and merged to develop.

I need more details about the third one:

As you can see with the above two pictures, hovering the filter box trigger the scrollbar which hide the majority of the filter himself, interacting with the filter is a lot more complicated.

I cannot reproduce it on Google Chrome, on Linux. Can you specify more details about browser/OS used?

Also, for the future, if you could open separate issues per problem, it would make things a lot simpler from tracking purposes.

[MilosPaunovic]

Only two things remain here:

1. Scroll issue (@ReLoutre if you could open separate issue with more details, that would be great)

2. As you can see with the above picture, green blocks, the field "next execution date" display a date for realTime triggers, which is weird, and what's more, it display instead the "creation date" i guess.

@Ben8t could give us more info about the second point, and will open a separate issue, if necessary.

@sanjaykumar584 We had to amend those issues quickly, so I took over. If you're still up for contributing, may I suggest that you check our curated list of good first issues to see if there is something you find interesting enough and think you can tackle independently. It can be further filtered by desired labels to narrow down the results (suggesting to filter by either area/backend or area/frontend ones, based on your preferences).

I am closing this issue now.

[Ben8t]

As you can see with the above picture, green blocks, the field "next execution date" display a date for realTime triggers, which is weird, and what's more, it display instead the "creation date" i guess.

RealTimeTriggers have waitTime and conditions properties so it make sense in some cases to have "next date". I believe it's best to see this "next execution date" as the next "evaluation" of the trigger in case of RealTimeTrigger.

Still I agree, "create date" and "next execution date" should be different. Can you open a dedicated issue for this @ReLoutre please ?

[ReLoutre]

Hi @MilosPaunovic ,
Sry for the listing thing, thought it was a good idea (fail happens).

Regarding the third point :

• I'm mainly using Firefox
• I'm accessing the web page through a windows 10 os
• Problem is that interacting with crosses of the filter are a bit tricky (while it's still possible) since the hovering box of the scroll bar seems to reach the center of the filter box
  
  
• New info, seems like zooming out (even by 10%, so having a zoom of 90% instead of 100%) make the scroll bar completely disappear. And while zooming in up to 200% the scroll bar disappear as well. On some pages in does not appear and some other it does. And most of the time, it appears while not being useful at all (since the filter is already completely visible, while in some case it could be useful but it doesn't appear). The behaviour of this scroll bar is highly inconsistent. Having it under the box could be good.

Useful but do not appear :

Useless but appear :

[ReLoutre]

As you can see with the above picture, green blocks, the field "next execution date" display a date for realTime triggers, which is weird, and what's more, it display instead the "creation date" i guess.

RealTimeTriggers have waitTime and conditions properties so it make sense in some cases to have "next date". I believe it's best to see this "next execution date" as the next "evaluation" of the trigger in case of RealTimeTrigger.

Still I agree, "create date" and "next execution date" should be different. Can you open a dedicated issue for this @ReLoutre please ?

I'm on it @Ben8t !

[ReLoutre]

Scroll issue (@ReLoutre if you could open separate issue with more details, that would be great)

Forgot to make it separate, i'll do another issue too.

[ReLoutre]

Here's the two new issues :
#6338
#6340