Two separate Jira requirements having links to the same reusable test case and executed in different test cycles and having the automatic traceability test player set to when adding/creating issue to add the issue to the requirements covering the test case -the bug/issue is added to all traced requirements. The bug currently is being linked to past requirements (packages, story, config, development) even though the requirement under testing now or today is only failing for one of the traced requirements. This is inaccurate.
|I would like...||the test player screen when adding/creating an issue to display a picklist of requirements covering the test case|
|So that I...||select which requirement the issue is traced to. Instead of the new issue being traced to new requirement and all previous requirements.|