effects: plugin v 0.6.11 , sentry v 5.1.0, and JIRA v ???
env: hosted sentry
Only logged once, I suspect that there's some weird way around the configuration that's allowing the form to never get it's issue_type populated.
should both assert that the issue_type is there, and plug the configuration hole.
AttributeError: 'JIRAIssueForm' object has no attribute 'issue_type'
Stacktrace (most recent call last):
File "django/core/handlers/base.py", line 111, in get_response
response = callback(request, *callback_args, **callback_kwargs)
File "sentry/web/decorators.py", line 154, in wrapped
return func(request, *args, **kwargs)
File "sentry/web/decorators.py", line 77, in _wrapped
return func(request, project, *args, **kwargs)
File "sentry/web/frontend/groups.py", line 364, in group_plugin_action
response = plugin.get_view_response(request, group)
File "sentry/plugins/base.py", line 313, in get_view_response
response = self.view(request, group)
File "sentry_jira/plugin.py", line 131, in view
ignored_fields=self.get_option("ignored_fields", group.project))
File "sentry_jira/forms.py", line 135, in __init__
"Error communicating with JIRA, Please check your configuration."]
File "django/forms/forms.py", line 115, in _get_errors
self.full_clean()
File "django/forms/forms.py", line 271, in full_clean
self._clean_form()
File "django/forms/forms.py", line 299, in _clean_form
self.cleaned_data = self.clean()
File "sentry_jira/forms.py", line 203, in clean
fs = self.issue_type["fields"]
effects: plugin v 0.6.11 , sentry v 5.1.0, and JIRA v ??? env: hosted sentry
Only logged once, I suspect that there's some weird way around the configuration that's allowing the form to never get it's issue_type populated.
should both assert that the issue_type is there, and plug the configuration hole.
tagging @dcramer so he's in the loop.