When linking a Test to to a Story, the test case importer picking the wrong issue link type if the two issue link types have the same description.

Description
When linking a Test to to a Story, the test case importer picking the wrong issue link type if the two issue link types have the same description. 

When importing tests and linking requirements with tests, we used the link type "tests" in the mappings. However, if the issue linking has the same description, it shows multiple values because we created the same description for two link types.

After importing, regardless of which option was selected while mapping the link type, the test coverage always shows as uncovered.

Pre-conditions

How to reproduce{}

1. Create a new Issue link type with same description as shown in the below screenshot.
   
2. Create a CSV to link Test to a story.
3. Do the mappings for linking the Test with story.
4. As we have the links types with same description it shows multiple options in the dropdown.
   
5. You can use 1st option in one attempt and Import it.
6. Test coverage shows uncovered.
7. Try with 2nd option in another attempt.
8. Still the Test Coverage showing uncovered.

Actual result/Attachments

Test Case Importer picking the wrong Issue link type.

When importing tests and linking requirements with tests, we used the link type "tests" in the mappings. However, if the issue linking has the same description, it shows multiple values because we created the same description for two link types.

After importing, regardless of which option was selected while mapping the link type, the test coverage always shows as uncovered.

Expected result
It should pick the correct one as default

Version

• <app versions>