It’s certainly possible for New Relic customers to roll their own and call Atlassian APIs and create issues related to New Relic errors or slow traces. Or to use a browser extension like Zephyr Capture, or the direct-link method described in the top post. Those solutions aren’t ideal, I realize, since they don’t result in the New Relic error or trace storing the associated Jira issue so that you can track that relationship within the New Relic troubleshooting UIs. We definitely hear your feedback about that being a valuable capability.
So while we don’t have it in our immediate plans to reintroduce this capability for Jira, your feedback here is emphasizing that we could serve our customers well if we brought it back! Thank you for piling on here