Allure: Assign ID" overwrites existing valid @AllureId despite documentation guaranteeing annotated tests are skipped

[ivan-ramanovich]

Component: Allure TestOps IntelliJ Plugin — "Assign ID" action
Plugin version: 3.21.3
IDE: IntelliJ IDEA

Summary
The "Allure: Assign ID" action overwrites an existing, valid @AllureId annotation on a test that is already linked to a test case in Allure TestOps. This directly violates the documented contract:

▎ "Tests without @AllureId will have annotation added; tests already annotated will skip assignment."
▎ — JetBrains IDE plugin docs, Workflow 2 (https://docs.qameta.io/allure-testops/ecosystem/intellij-plugin/)

As a side-effect, the new ID was assigned to two different test methods simultaneously, creating a duplicate @AllureId in the codebase.

Environment

• Test framework: JUnit 5
• Allure Java annotations: io.qameta.allure.AllureId
• Build tool: Gradle
• Language: Java

---

Steps to Reproduce

1. Have a test class containing two test methods in the same file:

• Test A — has @AllureId("143049"), already linked to an active test case in Allure TestOps
• Test B — has no @AllureId, is a new test that has been uploaded and whose launch has been closed in TestOps (auto-created as test case 147433)

2. Right-click the package or class in the IDE
3. Select "Allure: Assign ID"
4. Select the TestOps project

---

Actual Result

• Test B receives @AllureId("147433") ✓
• Test A's @AllureId("143049") is overwritten with @AllureId("147433") ✗ — both tests now share the same ID
• Allure TestOps still shows test case 143049 as the active case for Test A, confirming the original annotation was valid at the time of overwrite
• No warning, confirmation dialog, or diff preview was shown before the annotation was changed

Git diff confirming the issue (from actual occurrence):

• @AllureId("143049")

• @AllureId("147433")
  void shouldReturnConsistentOffersAcrossPages() { ... }

• @AllureId("147433")
  void shouldReturnConsistentOffersAcrossPagesWithCountryFilter() { ... }

---

Expected Result
Per the documented behaviour of "Assign ID":

• Test B receives @AllureId("147433") ✓
• Test A is skipped entirely — its @AllureId("143049") remains unchanged ✓
• No two test methods share the same @AllureId value

[cheshi-mantu]

@ivan-ramanovich thanks for reporting this
We would appreciate if you use recommended channel for Allure TestOps users that lives here https://help.qameta.io, so we address such issues faster (see here: https://docs.qameta.io/support/#help-desk-portal).

Could you please check if you have this configuration parameter checked ?

If it's off, please enable it and retry. Should the issue persist, please let us know via https://help.qameta.io, we would need some extra details we would like to avoid to be in the public resources.

[ivan-ramanovich]

@cheshi-mantu hello! Thank you for the response. I just added the toggle and the issue is gone.

[cheshi-mantu]

fixed