Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit?

Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration.

What impact would it make?

Prevent failure of the integration (which took us several hours to figure out).

This was particularly egregious for us because we have swapped the names "Feature" and "Epic"... with the "Feature" being the large piece of value that we're roadmapping for customers and "Epic" being the subcomponent that's being sent to Jira as epics in that system. (We then use "requirements" to map to stories).

How should it work?

The resource types in the Jira mapping should respect the custom terminology.