You can choose to map both Elements requirements and stories to multiple issue types in Jira. To do this, once you have connected your Jira instance to Elements, click the "Add issue type" button. This will open the following window, where you can choose your mappings:

Once you confirm a mapping you can't change the issue types you have mapped. Instead you will need to delete the issue by clicking "Delete issue type" on the issue:

You can map Elements requirements to Jira Epics, or Epic "level" issue types (i.e. a high level issue that can have multiple children issues associated with it).

To map requirements to Epics, simply select "Requirement" as the Elements issue type, and "Epic" as the Jira issue type:

Note that when linking Elements requirements to Jira epics we don't track parent-child relationships across the 2 systems. If you change the parent requirement of a story in Elements, you will need to change the Epic in Jira too. However, the statuses and fields for each respective issue will remain synchronised.

To map stories in Elements to stories or story level issue types in Jira, simply select "Story" as the Elements issue type, and then select the Jira issue you want to link. In the example below we've chosen Bug:

You can connect your requirements and stories to more than one issue type in Jira, you are not limited to a 1-to-1 relationship. Simply keep adding issue types in the Elements setup until you have achieved the configuration required for your workflows.

See here for more on sending stories to Jira.

If you have connected multiple issue types to your Elements requirements/stories, you will have to choose the issue type when sending to Jira. This is done from the right panel of the issue you want to send. After clicking "Send to Jira" a dropdown will appear where you select the issue type you want to create:

The same is true for Bulk sending issues to Jira. After right-clicking "Bulk send to Jira", a window will appear where you must select the issue type for all issues that will be created in Jira:

Once you've connected the issue types you will want to look at mapping the fields and status workflows to match your requirements. See here.