As a user, I would like to map Gherkin scenarios in feature files to existing Tests using issue key tags (ex.: @ABC-123)

Current behavior:
When importing Gherkin feature files into Xray Cloud, scenario-to-Test mapping is currently based primarily on the scenario name. If the scenario name changes between imports, Xray Cloud creates a new Test issue instead of updating the existing one.

Xray Cloud also supports mapping scenarios to existing Tests using local tags with internal IDs (such as @id:1 and @id:2). When these tags are present, Xray correctly updates the corresponding Tests even if the scenario name changes.

Current limitation:
While functional, the use of local @id tags can become difficult to manage at scale, particularly in environments with hundreds or thousands of feature files. These internal IDs are not inherently meaningful outside the file itself and can be hard to track, audit, or refactor over time.

Desired implementation:
In Xray DC, scenario-to-Test mapping could be performed using tags that reference the Jira issue key directly (ex.: @ABC-123). When such a tag was present, Xray would reliably identify and update the corresponding Test issue, regardless of scenario name changes.

This approach provided:

• A clear and explicit link between scenarios and Jira issues
• Easier long-term maintenance of feature files
• Better traceability and readability for large test repositories

For this reason, as I user, I would like to be able to map Gherkin scenarios in feature files to existing Tests using issue key tags, in addition to the current @id-based mechanism.

This would allow Xray Cloud to:

• Update existing Tests even when scenario names change
• Align Cloud behavior more closely with Data Center capabilities
• Improve maintainability and clarity for large-scale Gherkin test suites