Jira Issue Type is incorrect with Next-Gen projects

[alexeSGN]

It looks like the Next-Gen Jira projects create duplicate issue types with a project scope of the new project. Even in the Jira user with API Token does not have access to that project the issue_types come up in the Jira Python 2.0+ client.issue_types() method, which means that the jira_session.py#480 self.issue_type_by_name(issue_type) call returns a scoped issue type which most projects can't use.

It looks like using issuetypeNames=issue_type in the self.createmeta(...) on line 489 would be preferable to using that queried id, since the createmeta data will be correctly project scoped.