Feature Request: Add UI filter for Playwright Projects / Devices

[yozh150991]

Is your feature request related to a problem? Please describe. Yes. When running a cross-device or cross-browser testing matrix using Playwright, all test results are aggregated into a single Allure report. While we can see the project/device context inside individual test execution details, it is difficult to filter the overall dashboard, suites, or graphs to see the stability of a specific device. We need an easy way to isolate failed or successful tests by the device they were run on.
Describe the solution you'd like I would like a global filter option (e.g., a dropdown or toggle button) in the Allure Report UI—specifically on the Overview, Suites, and Behaviors tabs—that allows users to filter the displayed test results by "Project" or a specific "Device" label.
Ideally, the Allure reporter would automatically parse the project.name from the test runner and expose it as a top-level filtering parameter in the generated HTML report.
Additional context We configure our devices as Playwright projects. Here is an example of our setup:

TypeScript
projects: [
{
name: Devices.Desktop,
use: {
...devices['Desktop Chrome HiDPI'],
launchOptions,
},
},
{
name: Devices.Mobile,
use: {
...devices['Pixel 7'],
viewport: { width: 412, height: 915 },
launchOptions,
},
},
{
name: Devices.MobileLandscape,
use: {
...devices['Pixel 7 landscape'],
viewport: { width: 915, height: 412 },
launchOptions,
},
},
]

When tests fail, we need to be able to quickly select
Devices.Mobile from a filter dropdown in the Allure report to see exclusively which tests failed on the Pixel 7, rather than having them mixed in with the Desktop results.

[todti]

Hi! There are two clean ways to do this in Allure 3, both without changing your tests.

Option 1 — Environments (single report, device switcher)

Configure each Playwright project as an Allure environment in allurerc.mjs. Allure 3 generates per-environment data and adds a switcher to every view (Overview, Suites, Behaviors) automatically:

// allurerc.mjs
import { defineConfig } from "allure";

export default defineConfig({
  environments: {
    desktop: {
      name: "Desktop Chrome",
      matcher: ({ labels }) =>
        labels.some((l) => l.name === "parentSuite" && l.value === "Desktop Chrome"),
    },
    pixel7: {
      name: "Pixel 7",
      matcher: ({ labels }) =>
        labels.some((l) => l.name === "parentSuite" && l.value === "Pixel 7"),
    },
  },
});

This works because allure-playwright already sets project.name as the parentSuite label on every test result — no extra annotation needed.

Option 2 — Separate reports per device

Run each Playwright project separately and generate a dedicated report for each:

npx playwright test --project "Desktop Chrome"
allure generate allure-results --output reports/desktop

npx playwright test --project "Pixel 7"
allure generate allure-results --output reports/pixel7

Or configure resultsDir in the reporter options to isolate results from the start:

// playwright.config.ts
reporter: [["allure-playwright", { resultsDir: "allure-results" }]],