Issue Summary

When using a Plan with multiple projects in its issue sources, if you have components with the same name but from different projects, grouping them together in the View settings will block you from creating issues under the component.

Steps to Reproduce

1. Have a Plan and add more than 1 project in the issue sources
2. Create the same Components in 2 or more of these projects (eg. Housekeeping)
3. In the View settings of your Plan, group by Component and add the different Housekeeping component into 1 group
4. Create an issue right under a parent so it automatically takes the component

Expected Results

After saving the changes, this should create the issue under the parent and take the component value.

Actual Results

Changes couldn't be saved

{"success":false,"error":{"error":"ISSUE_CREATE_EXCEPTION","errorMessages":[],"exception":{"type":"com.atlassian.rm.jpo.core.scenario.common.data.ScenarioCommitException","message":"Scenario commit error","stackTrace":[]}},"change":{"sequence":{}}}
{
    "success": false,
    "error": {
        "error": "ISSUE_CREATE_EXCEPTION",
        "errorMessages": [],
        "exception": {
            "type": "com.atlassian.rm.jpo.core.scenario.common.data.ScenarioCommitException",
            "message": "Scenario commit error",
            "stackTrace": []
        }
    },
    "change": {
        "sequence": {}
    }
}

Workaround

The duplicate name components should be in separate groups, otherwise, there is no other known workaround for this behavior.