Some things needs fixing, before associated PR can be merged:
The PR is merely implementation of topic, discussed in the issue. Since PR come and go, but issue itself stays, then it must have proper description and not other way around.
The title of an issue is not very descriptive. I know (from our prior communication), that you want to support scopes of an issues type entity, but issue title itself doesn't even partially resemble that. Also no need for a trailing dot, because issue/pr title isn't a sentence :)
Some time ago JIRA API was changed and now
scope
is returned as part ofissuetype
properties in the list of returned issues (see https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-api-2-issueLink-linkId-get).Since it's not explicitly whitelisted in
\chobie\Jira\ IssueType::$_acceptableKeys
property the exception is thrown during API response parsing.Closed by #181.