Hi, @sharovd

Thank you for investing your time in allure-pytest.

The thing is that allure-pytest is unique among other Allure integrations in that it tries to convert to tags something that doesn't really fit into the idea of tags: pytest markers with arguments. I believe implementing this was a mistake, as it creates more problems than it solves. We shouldn't also convert built-in markers, as we have better options to indicate their effect. I've described it in more detail in the issue.

And if we don't convert the abovementioned markers, the problem with missing tags will resolve itself (multiple markers with no arguments means the tag values will be the same, and there is no point in having multiple tags with absolutely the same values).

We have an existing issue that addresses just that: #817, and we should implement it. If you're still willing to work on markers-to-tags conversion, you may take the implementation from allure-pytest-bdd and adjust the tests accordingly.

@delatrie, hi!
Thanks for the details, and sorry for the delay from my side.
I’ve looked into issue #817 and suggested a solution in PR #862 - please review.
I believe we can now close this PR?

@sharovd , thanks for addressing it so quickly. I'm closing this PR in favor of #862 now