How filter parameters for Report Portal 5.5.0 works?

[Itso-Dimitrov-Syncplicity]

In Build: 4.3.0 we can specify directly in the URL parameters to create filters for specific report portal record
Ex: launches/New_filter?page.page=1&page.size=50&filter.has.tags=Jenkins_Run:{BuildNumber}

for Build: 5.5.0 i tried with - launches?filter.has.attributeValue={BuildNumber}&filter.has.attributeKey=Jenkins_Run'
but that did not work.

How we can specify such for Build: 5.5.0?

[evjlobanova]

In version 5.5 there is no such functionality.
Right now, I can propose a workaround.
You can create a basic filter for instance based on the launch name.
Then you can create a widget Component Health Check View

And specify for this widgets option: key value Build

In this case the system will group launches and tests around attributes with key Build and with unique Values.
This widget has clickable links, so that if you click on the panel

The system redirects you to the page with tests from launches with specified build:

And now the workaround)):
The link has the format:

https://localhost:8080/ui/#Project_Name/launches/6264/list?item0Params=filter.eq.hasStats%3Dtrue%26filter.eq.hasChildren%3Dfalse%26filter.in.type%3DSTEP%26filter.has.compositeAttribute%3Dbuild%253A3.23.11.37.18%26launchesLimit%3D600%26isLatest%3Dfalse%26filter.in.status%3DPASSED%252CFAILED%252CSKIPPED%252CINTERRUPTED

So that if you have already created a widget with grouping around the build, you will be able to generate a link to the new builds.

In version 5.6 - we will provide a more convenient way to do this operation.

[Itso-Dimitrov-Syncplicity]

Thank you for the reply @evjlobanova :)
I tried your suggestion and it worked, but is there a way to be redirected on the page launches not in the test results with specified build number in the url?
Ex:

[mcookson3]

@evjlobanova You mentioned above that there would be a more convenient way to do this in 5.6, but I looked at the release notes for 5,6 and I don't see anything about a fix for this. Is that still in the works?

[pulse00]

@evjlobanova same here - any info on this? 5.7 does also not mention this issue.

[Zenin-Dmitry]

@patsevanton I also find the launch filter by attribute in the url useful. I run a lot of tests where one of the attributes is $CI_COMMIT_SHORT_SHA.
I want to generate a link to the passage of all test runs with this attribute. This link will then be included in the email template for testers.