Exporting Cucumber Features via REST API and from the Coverable Issue Key is causing a mismatching in the @REQ tag and its correspondent coverable tests

Short Description: Exporting Cucumber Features via REST API and from the Coverable Issue Key is causing a mismatching in the @REQ tag and its correspondent coverable tests.

Short Description:

1 - Make sure that there aren't next gen projects in your environment

2 - In a project, create the following structure:

> EPIC-1
>> STORY-1
>>> TEST-1
>> STORY-2
>>> TEST-2

3 - Via REST API, export the cucumber feature from the Epic issue key

Actual Result:

The @REQ tags on the test cases will all point to the same story, i.e.:

TEST-1: @TEST_TEST-1 @REQ_STORY-1
TEST-2: @TEST_TEST-2 @REQ_STORY-1

Expected Result: 

The @REQ tags on the test cases should point to the correspondent linked stories, i.e.:

TEST-1: @TEST_TEST-1 @REQ_STORY-1
TEST-2: @TEST_TEST-2 @REQ_STORY-2