Issue with Allure Reporting Structure for Playwright + PyTest

I am currently working on integrating Allure reporting with our Playwright Python test suite, and I’ve encountered a limitation in the reporting structure that impacts test readability.

Issue Description:
We are using with allure.step(...) blocks inside a single test function to log detailed steps

(e.g., Login into the application,
Select use case,
Verify Ongoing Threads UI,
Ask Question .. etc.).

These steps correctly appear under Execution → Test body in the Allure report.
However, they do not appear in the left-side panel under the test title. The sidebar only shows the main test case title (e.g., Verify OngoingThreads UI elements), making it harder to quickly identify which step passed or failed and how much time each step took.

Current Behavior:
All steps are nested inside one test case.
Sidebar shows only one entry per test function.
Execution details (steps and timing) are visible only when expanding the test case.

PFA

Expected Behavior:
Each major step (or at least its name) should be visible in the left-side panel under the main test title for better visibility of:
Which step passed or failed
Execution time per step
Overall progress during test runs

Module1
Epic/Story1
Title1
--Test step1
--Test step2
--Test step3
Epic/Story2
    -Title1
--Test step1
--Test step2
--Test step3

Impact:
Difficult to quickly analyze failures and performance at a granular step level.
Reduces clarity for stakeholders reviewing reports.
Current Implementation:
Using pytest.mark.asyncio for async tests.
Allure decorators like @allure.epic, @allure.story, @allure.title for grouping.
Steps logged with with allure.step(...) inside a single test function.
Question:
Is there a recommended approach or configuration in Allure to display these steps in the sidebar?
Alternatively, should we split each major step into separate test functions with individual @allure.title annotations for better visibility?
Attached:
Screenshot of current Allure report structure.
Sample test code and conftest.py implementation for reference.

Start with the reported use of with allure.step(...) in the Playwright Python tests and the referenced sample test code and conftest.py. Review how @allure.epic, @allure.story, and @allure.title are represented in the generated report, then determine whether the requested sidebar hierarchy is supported or requires a defined change; done means the expected step visibility and timing behavior are established.

Rédigé par le modèle d'indexation à partir du texte de l'issue.