Sentry: Create Jira ticket with 'None' value in custom select field

Created on 2 Jun 2017  Â·  2Comments  Â·  Source: getsentry/sentry

When using the Sentry UI to create a new Jira issue, the UI doesn't seem to respect the default value of 'None' for a custom select field.

Here is the config in Jira
image

Here are the options in Sentry
image

Notice how there is no option to select 'None'.

Most helpful comment

When the jira screen is first loaded, this custom field appears like it has a value:

image

But looking at the react devtools, the state.value is "". Once I click an item, state.value changes to an id.

I notice there's an allowEmpty prop which is set to false, but setting it to true doesn't seem to clear the value in the UI — not sure what's up with that.

So if you create an issue without touching the select field, you can create an issue without having to pick an option. This is a decent workaround for this bug.

All 2 comments

When the jira screen is first loaded, this custom field appears like it has a value:

image

But looking at the react devtools, the state.value is "". Once I click an item, state.value changes to an id.

I notice there's an allowEmpty prop which is set to false, but setting it to true doesn't seem to clear the value in the UI — not sure what's up with that.

So if you create an issue without touching the select field, you can create an issue without having to pick an option. This is a decent workaround for this bug.

Closing this issue due to staleness. Feel free to comment here if you think we should still work on this.

Was this page helpful?
0 / 5 - 0 ratings