How to track Traceability from Cucumber-report Feature file and Scenario to the corresponding story

[Mathew]

How to track Traceability from Cucumber-report Feature file and Scenario to the corresponding story and Epic in Jira?
ie from Cucumber-report  Feature file and Scenario how I can track to which Story and Epic this Scenario belongs in Jira?

I'm newly joined to a Jira scrum project, the technologies used in this project are, Cucumber, Jenkins, and Jira Scrim. (Cucumber Automation is done by a separate team).

I'm asked to do the traceability from the Cucumber report to story and Epic.

Thank you in advance

[JamieA · Accepted solution]

No, because if he can run jelly scripts, he has full access and could make himself an administrator with the right jelly script. We can give better suggestions if you tell us what he wants the jelly scripts for?

[Wayne Izatt]

Cool. That's what I figured.

He needs to be able to automatically close issues that haven't been replied to, basic issue escalation sort of stuff.

[JamieA]

Yeah... if he wants to do that sort of thing himself you could point him to the remote API. That stuff can be accomplished with user level perms and the SOAP or REST API.