How can I create issues from emails in a project w/ mandatory fields whose value is not in the email

[Rob Horan]

Assume the content of the email cannot be modified to include the field value.

I have a project with a mandatory single select field shared by 3 issue types.

The incoming email will not contain a value for this field.  Is there a way to have Jira automatically set a value when creating the issue by email?

Using a default value is not ideal because people can create issues manually, and all of the issue types will then use this default, which leaves the possibility that this field can be left in place when manually created.

Using a field context to limit this default to one issue type is also not ideal because then the options list will need to be maintained in two spots, and updates to the options are semi-frequent. 

Making the field optional is not an option because there are post-functions that rely on this value that will not work if the field is empty.

Buying JEMH is not an option.  The user tier on this instance makes the licensing cost far too high.

Is there a way to have a default value that could be used for email, but with a mechanism in place that requires users to make a selection when manually creating issues?

Scriptrunner is installed. I can't write Groovy script for ----, but... if I know its possible that's a starting point?

[Boris Berenberg - Atlas Authority]

Hey Rob,

We're a fair bit cheaper than JEMH and offer the ability to set a default value for a field on issue creation: https://marketplace.atlassian.com/apps/1216597/in-mail-handler-pro?hosting=server&tab=overview

Boris

[Rob Horan]

Hi Boris, thanks for the info.  Buying any plugin for this particular instance is going to be an uphill battle  I will review this and present it if it offers a solution.  Thanks!