Currently if you pass a instance URL that's ending with / the rest of the code will fail. The system should either strip the / or use a different function that doesn't duplicate the /.

JIRA sends back an autocompleter url that will return filtered users. Implement some sort of autocompleter widget that uses this.

note: currently there is no easy way to include your own static media as a plugin, so JS would have to be included directly in the template 👎 -- 👍 can now since sentry 4.10.0

Passing on a report, but it seems that when you change the issue type (e.g. to Bug), the Epic Name field is still required.

To the actual report, which might contain some more useful information:

"The Epic Name field is required (This field is required. if submitted empty), but is not present on our Bugs, which leads to "Field 'customfield_12101' cannot be set. It is not on the appropriate screen, or unknown." if I submit with a value in the field, "

Could there be an issue with how its refreshing required fields when you select other issue types?

On creating new jira issue getting this error even issue type is set. Tried to change it and change other fields doesn't help.

If a field is ignored (via ignored fields) errors related to it do not get displayed

on hidden fields, labels are shown but fields are hidden. I think its a shortcoming of the template used to render the form

Using the SaaS Sentry (getsentry.com) and JIRA OnDemand (COMPANY.atlassian.net), we can set the URL, the username, and the password correctly and get the message “Your settings were saved successfully.”; this does not result in the second phase of configuration (selecting a project, etc.).

getsentry.com is reporting that it's using version 0.8.0 of sentry-jira. If it matters, our JIRA OnDemand also has a Confluence instance attached. I don't think it does; it seems that there's something else wrong, but I don't have enough information or insight into what it is.

Because I can't select a project, I also don't see the option to submit an issue via JIRA. Any advice?

a custom field that is of type select will require parsing of allowedValues, and sending back the result in a JSON object to the API.

currently, if you fill out the field, it will fail with a message like: "Could not find valid 'id' or 'value' in Parent Option object"

sample field schema that will be supported:

{
   u'required':False,
   u'schema':{
      u'type':u'string',
      u'custom':      u'com.atlassian.jira.plugin.system.customfieldtypes:select',
      u'customId':10420
   },
   u'name':u'Severity',
   u'operations':[
      u'set'
   ],
   u'allowedValues':[
      {
         u'self':         u'https://xxx/rest/api/2/customFieldOption/10010',
         u'value':u'Critical',
         u'id':u'10010'
      },
      {
         u'self':         u'https://xxx/rest/api/2/customFieldOption/10011',
         u'value':u'Major',
         u'id':u'10011'
      },
      {
         u'self':         u'https://xxx/rest/api/2/customFieldOption/10012',
         u'value':u'Minor',
         u'id':u'10012'
      },
      {
         u'self':         u'https://xxx/rest/api/2/customFieldOption/10013',
         u'value':u'Trivial',
         u'id':u'10013'
      }
   ]
}

cc @wolfe

When creating a jira ticket, it would be nice if we can choose the project on the fly. The use case for this would be a sentry project associated with multiple jira projects where the jira project could refer to different departments (eg. QA, Dev, OPS, Marketing, etc.) So, when a jira ticket is created, it would assigned to different departments first for investigation.

As you have mentioned before, the crumby part about allowing to configure the project
per issue is that it is a 3 step process. This would be to select a project, query the project meta from the API, select the issue type, grab the custom fields for that type, then display the form.

In the version of sentry-jira installed on getsentry.com, if I create an issue but don't select an Assignee, the issue created has the same Assignee as the selected Reporter - I would expect it to be assigned to Unassigned.

When multiple events are triggered in Sentry, it would be great to be able to create tickets and append other events onto the creation of that ticket.

Also, it would be nice to just be able to define a pre-existing ticket to link the event to, maybe even have it comment on the ticket.

currently lives in models, very unintuitive.

When attempting to configure the plugin I get Unable to connect to JIRA: Bad Response. We're using Atlassian Ondemand Jira, which up until a recently, this plugin worked with. Not sure if there's something on the Ondemand side that broke this.

I added a resource_links attribute in plugins to improve the interface. It renders like this in master:

http://cl.ly/image/1k2d0K0T3G1c

Just set resource_links to a list of tuples, like this:

    resource_links = [
        ('Bug Tracker', 'https://github.com/getsentry/sentry-github/issues'),
        ('Source', 'https://github.com/getsentry/sentry-github'),
    ]

submitting an invalid issue (that is form valid, but not JIRA valid) throws a key error.

take the response from JIRA and display it in a nice way, and re-display the form accordingly.

nicetohave: align the error message with the field in the form

At the moment, notifications of the JIRA being created is set in the configuration.

That means it is always sent from the one person.

Since the person whom the JIRA is assigned may follow up with more questions.

They would be confused to know the person who sent them the email (presumably the person raising the JIRA) does not know anything about the JIRA.

So to eliminate the confusion, I propose that notification emails should be sent from the logged in user, or alternatively the Reporter.

Our JIRA is firewalled (visible to Sentry, though), and we only have a self-signed certificate for it. When I put in my JIRA configuration and credentials, the connection fails with a log message like this:

ERROR:root:Error in request to https://jira/rest/api/2/priority: [Errno 1] _ssl.c:499: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Our certificate doesn't verify against any standard CA, so the answer is probably figuring out how to get a CA installed in a way that's visible to our sentry install so that this libssl (or whatever) call can validate it.

Chances are this is a wont-fix, because there's really nothing you can do about a bad certificate, but I'm making a ticket anyway, just in case someone else has solved this problem. I'll update if I find a good solution, of course.

"Another nice related tweak (I'm looking to have the fewest number of required fields) would be to make Reporter optional, and if it's not supplied, use the user that was specified when setting up the connection to Jira. My workflow for this is that we've got one "user" which is only used for the Sentry connection, so having all the things be "reported" by them would make it really easy to track all the bugs that come from Sentry."

cc/ @dlanger

different issue types can have different required fields or displayed fields.

use the createmeta jira api to get a list of required fields and display those dynamically.

some JIRA configurations have a TON of fields that are optionally available for issues, so the configuration form should give you the ability to filter out some of those optional fields.

minimum viable: comma separated list of field names to exclude
nicetohave: interactive list or visual form editor

Should I be able to use this plugin with my Google Apps account?

When I try those credentials, I get:

Unable to connect to JIRA: 401

The not_configured template render line should be:

            return self.render(self.not_configured_template, {
                'title': self.get_title(),
                'project': group.project,
                'has_auth_configured': has_auth_configured,
                'required_auth_settings': required_auth_settings,
            })

We should probably make this easier to extend. Open to ideas

When configuring the plugin, I enter the following information:
Instance URL: https://company.atlassian.net
Username: tolmstead
Password: mypassword

I click save changes, the page refreshes, but I am not presented with the option to select a project.

I am an administrator for this JIRA instance. I've tried with both firefox and chrome.

pip install doesnt work currently due to missing package information (sentry_jira doesnt actually get installed)

You can use packages=find_packages() in setup.py to fix the dist

See https://github.com/getsentry/sentry-github/blob/master/setup.py#L33 for an example

When creating a JIRA ticket in Sentry, the "Fix Version/s" field (which is part of the default config on our OnDemand JIRA instance) is reported as required, but it isn't actually required within JIRA.

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"]

tagging @dcramer so he's in the loop.

I've successfully configured against an OnDemand instance, but I need to refresh the config to update the list of available projects. I don't see how do to this, and further I can't seem to even clear the config. (I've tried disabling the plugin, changing values, etc. but nothing seems to work).

A nice addition would be if it would be possible to assign an existing Jira issue to a Sentry group.

Currently, multiselect and select boxes look sorta janked. I like the way select2 does it, and we can probably leverage it for the user autocompletion.

unblocked by: getsentry/sentry@9723689

currently any entered fields get bumped out and reset.

even though many fields can change based on issue type, it would be nice if matching ones persisted across type changes.

Jira Ticket should be added with a weblink to the Sentry Exception, instead of having the link pre-populated in the description field.

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

Firstly, this is brilliant. Thank you.

We have a lot of custom fields and it would be far easier for us to specify a list of fields that we do want in the form rather than a list of fields that we don't.

Getting rid of some of the old tables in the new version seems to have broken things:
Error processing 'actions' on 'JIRAPlugin': relation "sentry.group_meta" does not exist

show error messages for:

• unable to contact JIRA instance
• bad un / pw
• could connect, but wrong URL

make sure instance url gets saved without the "/"

Specifying a label (either a New Label or an Existing Label) results in the following error on submit: "string expected at index 0"

Error is shown Below the "Label" form field.

Several people have asked to be able to change the default issue type

Using getsentry.com's sentry-jira, filtering out custom JIRA fields doesn't seem to work.

As an example, I'll fill that field on the configuration screen with "components", but the Components field still shows up on the "Create JIRA Issue" screen.

I am using the following: Python 2.6, Sentry 5.0.14, sentry-jira plugin 0.6.7 and jira 5.1.4

This seems to be related to this issue (#20 and #23).

When I am submitting the jira ticket, it now complains about the "Fix version/s" which gives this error and it does not allow the jira ticket to be submitted.

"Field 'fixVersions' cannot be set. It is not on the appropriate screen, or unknown."

I tried to put any values but it does not seem to be accepting it.

As a workaround, I had to comment out the following in forms.py:

# fixVersions = forms.MultipleChoiceField(
#    label=_("Fix Version/s"),
#    required=False
#)

....

# self.fields["fixVersions"].choices = self.make_choices(versions)

This seem to work. But I'm not sure what the effect of this would be.

I am using the following: Python 2.6, Sentry 5.0.14, sentry-jira plugin 0.6.6 and jira 5.1.4

I am able to successful configure the plugin and successfully linked the plugin to the jira server. I am also using the credentials of the jira administrator.

When I am creating a jira ticket based on a sentry issue, I see the following:
Error Communicating with JIRA, Please Check your configuration

and Issue Type is blank (there is nothing in the drop down menu).

I know that sentry can talk to the jira server because when I was configuring it was able to pull the different projects where it will be linked.

Let me know if you need any other information or if you need me to do something else.

When changing issue type in Sentry, the form is not changing depending on the required fields. Thus, we cannot create a JIRA task.
Thanks;
Paul

See https://github.com/getsentry/sentry-github/blob/master/setup.py#L40

This removes the need to add it to INSTALLED_APPS (so users can simply pip install the plugin)

I am using the following: sentry 5.0.12, sentry-jira 0.6.1, python 2.6.5.

When I try to add my jira credentials to Sentry, I get the following errors.

Internal Server Error

Then when I click on the associated sentry error that it generated, I got this and I'm just adding some snippets that I think are relevant.

sentry.web.decorators._wrapped
root AttributeError: 'module' object has no attribute 'OrderedDict'

Location: sentry_jira/jira.py, init:85

"SSLError(SSLError(SSLError(1, '_ssl.c:480: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknow"
{'content-type': 'application/json'}
'get'
'<sentry_jira.jira.JIRAClient object at 0x98b7a4c>'
u'https://192.168.56.110:8080/rest/api/2/priority'

The sentry server can talk to the jira server on the specified port. So, I am not sure what is going on. Let me know if you need more info.

I have a case when JIRA usernames are exactly the same as sentry usernames and it would be great to have an option to make reporter field prefilled with sentry username on issue creation.