Reusing attachment source in multiple attachments results duplicate names and content types

[metafates]

Hello!

Noticed a bug in web-page generated by the allure generate command. It happens when reusing the same attachment source in multiple attachments with different names and types.

Given the following result

{
  "uuid": "c6986522-feaa-41c8-95bf-e3eb90fe73b0",
  "historyId": "a21f218dcda764be",
  "testCaseId": "5e57efda18f46b5c",
  "fullName": "Test/Suite/TestFoo",
  "name": "TestFoo",
  "description": "",
  "labels": [
    {
      "name": "suite",
      "value": "Suite"
    },
  ],
  "attachments": [
    {
      "name": "a json attachment",
      "source": "242eb08f-4dbf-4da0-bb67-62cd505e4495-attachment.json",
      "type": "application/json"
    },
    {
      "name": "a yaml attachment",
      "source": "242eb08f-4dbf-4da0-bb67-62cd505e4495-attachment.json",
      "type": "application/yaml"
    }
  ],
  "status": "passed",
  "statusDetails": {
    "known": false,
    "muted": false,
    "flaky": false,
    "message": "",
    "trace": ""
  },
  "start": 1763710761528,
  "stop": 1763710761528
}

Allure report shows the following

And their types are shown as yaml for both.

Also, drop down works weird in such case

Screen.Recording.2025-11-21.at.10.52.10.mov

Expected

It is expected to show two attachments: a json attachment with its type set to application/json and a yaml attachment with its type set to application/yaml.

[baev]

As of now, we have no plans to support reusing the attachment source. Allure 3 and Allure TestOps already link files only to the first attachment link found. This decision was made as a performance optimisation to support realtime reports. For you to better understand, the issue is that if we allow attachments to be reused in multiple steps or results, we will have to store all the attachment files in raw format until all the results are processed and only then proceed with the cleanup. Instead, the first link to the attachment file now "consumes" it, and we can process the file right away (e.g. if we need to remove attachments from passed tests, it can be done immediately).

[metafates]

Thank you for the explanation.

Is it possible that you would reconsider such feature in the future or accept a merge request?

Why does it matter

Tests may (and usually are) share identical attachments, e.g. headers for all network requests.
There may be thousands of such identical attachments in the same report, therefore making whole report weight much more than it could be, thus resulting tens of gigabytes of unnecessary storage in the database over time.

Recent global DRAM/NAND crisis made memory expensive and such optimization could benefit a lot of users.

What I propose

• Allure adapters could (optionally) track these duplicates, write them once as a single file and reference across results and steps.
• Allure 3 and TestOps would only need to display drop-downs for such referenced attachments correctly