Submitting an issue through an issue collector with attempt to match submitter email address enabled may fail if the user exists on Jira without any application access

Issue Summary

When a user submits the form from an issue collector, it may fail on the following scenario:

• The issue collector is configured with Attempt to match submitter email address.
• The user from the email attribute used in the form is registered on Jira, but doesn't have any application access.

Submitting the form fails with an error on the Jira backend saying the matched user doesn't have an application access.

On the UI to create an issue collector there's a mandatory field to choose a default reporter with the following information:

Reporter for the issue. Used unless a reporter is matched to a Jira user with create issue permissions.

Although existing on Jira, the user doesn't have application access, hence not having create issue permission.
Therefore, the issue collector should use the default reporter instead of throwing an error.

This might be an issue for those customers synchronizing users from an external LDAP, even those that shouldn't have access to Jira.

Steps to Reproduce

1. Install a vanilla instance of Jira.
   • This was validated on Jira Software 8.13.10 and 8.20.1.
2. Create a new user without any application access.
   
3. Create a new Scrum project with sample data.
4. Add an issue collector to that project
   • On Match reporter choose Attempt to match submitter email address.
5. Create a sample HTML so you can add the issue collector to it.
6. Access the sample HTML from a browser and click on Provide feedback.
   
7. Fill in the issue collector form and use the email of the sample user created on a previous step.
   
8. Click on Submit.

Expected Results

The form is submitted without any error and an issue is created on Jira using the default reporter.

Actual Results

Submitting the form fails with the following error on the UI:

Oops! Something went wrong...
There was a problem submitting your feedback, likely due to the configuration of this form. You might want to contact the site owner to let them know about this issue.

The following error is added to the application log:

2021-11-19 17:19:46,599-0300 http-nio-48201-exec-2 ERROR user001 1039x424x1 kptx6c 127.0.0.1 /rest/collectors/1.0/template/form/bae3f051 [c.a.j.c.plugin.rest.TemplateResource] Detected errors in collector 'Test issue collector' (id: bae3f051, project SCRUM): [Sorry, you can't create any issues right now, as you need to have access to a Jira application to be able to create issues. To gain application access you need to be a member of a group assigned to an application.]

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.

While there's no direct workaround for this situation, an administrator may try the following:

• Use an LDAP filter to synchronize only users that should have access to Jira.
• Give application access to affected users.
• Configure the issue collector to Always use issue reporter.