alena-babrova

Hello @Admon85, As far as I see from the screenshot provided, someone "qa_user" changed status from SKIPPED to FAILED initially. Why do you think it was made "automatically"? Maybe you...

Dear @monk-ada, We have fixed the bug and released it in 24.1.1 version (api-service 5.11.1 - https://github.com/reportportal/service-api/releases/tag/5.11.1). Please, try it out.

Dear @nvborisenko, Could you please tell me what the plan is for the issue? Are we going to fix it in our .NET client?

Dear @nvborisenko, As we haven't received a reply from you, we'll close the issue for now. If you still have an idea about how to fix, please do not hesitate...

Hello @rplevka, Thank you for the input. I see that the suggestion may be useful for end users. We will discuss it internally with the team and decide whether it...

Hello @svaraksin-gd, I want to inform you that the bug is already fixed and will be released in version 24.2.

Hello @pondrejk, Thank you for the input. The suggestion is indeed valuable and can be convenient to all users. We have created a task within our development team to discuss...

Hello @Gruuuubik, Thank you for highlighting the issue. I've registered a task in our Team's backlog to discuss how we can improve the component behavior to resolve performance degradation for...

Dear @Gruuuubik, The issue is still in the approval stage to be taken into work. Once it is approved to any upcoming release, I will update the status here.

Hello @elife1, I want to inform you that possibility of using OpenSearch instead of ElasticSearch will be available in our next release (version 24.1). Stay tuned!