Multiple components with the same name prevents auto-population of component when created from board

Summary

JIRA contains the ability to pre-populate certain fields of new issues created directly from an agile board so that they remain on the board. However if the board is set up to filter only on a project and component and the same component name exists for another project the component will not be populated.

Steps to Reproduce

1. Create a JIRA Software project, “scrum1", and add the component ‘test’ to the project
2. Create a few issues with this component
3. Create a board based on the filter “project = scrum1 and component = test”
4. View the backlog and create a new issue by clicking on the + Create Issue option from the bottom of the backlog
   (the new issue should be created with the component - test)
5. Create a second JIRA Software project and add the component ‘test’ to it
6. Return back to the original board and create an issue. The issue will be created without a component, and therefore will not appear on the board

Expected Results

The issue should be created on the board as there is only one component being filtered.

Actual Results

The issue is created without a component and does not appear on the board

Workaround

Rename one of the components so that the component names are all unique.