You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
For whatever reason, the issue_type dict doesn't have a 'fields' key when it gets to line 189 in forms.py. This causes the get() call to return None, which doesn't have .keys() method.
I wrote a quick fix to keep things running, but I'm not sure if this is a symptom of a deeper problem.
Sentry v5.4.1
sentry-jira@master
The text was updated successfully, but these errors were encountered:
@nsu I just had another thought about this after re-reading the JIRA API docs.
"The fields in the createmeta correspond to the fields in the create screen for the project/issuetype. Fields not in the screen will not be in the createmeta."
Sounds weird, but is it possible that your JIRA configuration has a custom issue creation form, and no fields defined on it? That seems to be the only way (outside of possibly a permissions issue) that this problem could manifest.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For whatever reason, the issue_type dict doesn't have a 'fields' key when it gets to line 189 in forms.py. This causes the get() call to return None, which doesn't have .keys() method.
I wrote a quick fix to keep things running, but I'm not sure if this is a symptom of a deeper problem.
Sentry v5.4.1
sentry-jira@master
The text was updated successfully, but these errors were encountered: