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

Retries not visible on detail of launch #3954

Open
jakubvojacek-wandera opened this issue Aug 7, 2024 · 3 comments
Open

Retries not visible on detail of launch #3954

jakubvojacek-wandera opened this issue Aug 7, 2024 · 3 comments

Comments

@jakubvojacek-wandera
Copy link

We started to use retries reporting in our ReportPortal instance (UI v 5.7.3) and I can see that the launch had some retries on all launch pages. But when the launch is open there is no visible icon which feature had retries. But once the correct feature is opened we can see which scenario had retries again. This is OK when the launch has only one or a few features in it, but when there is a lot of them it is not possible to easily find one with retries.

All launches:
image
Detail of launch
image
Detail of feature
image

And it is even harder if there was no fails after retries, so spotting flaky scenarios is very hard

@AmsterGet
Copy link
Member

Hello @jakubvojacek-wandera !
Thanks for your request!
@Kozovskaya could you please take a look?

@Kozovskaya
Copy link

Hello @jakubvojacek-wandera
Your request is really valid one and might be useful also for other users who use thi functionality.
I'll create a ticket in our Backlog and we will try to adress it upon team availability.
Thanks for highlighting

@Kozovskaya
Copy link

Hello @jakubvojacek-wandera once again
We've discussed your issue with the team. Unfortunately the issue requires significant changes. As for now our dev team is busy with other task of higher priority, but the ticket is in our backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants