Issue Description

Currently, editing the new parent field via the "Edit issue" action allows you to set that field by either copying from the trigger or current issue. You can also manually type in an appropriate issue to hard set it as well.

However, this fails when you enter in an issue with a key that ends in a number, instead of a alpha-character. Entering in an issue with a number at the end of the key does not let you press enter to accept it, while entering an issue without a number at the end of the key does.

For example, the following works:

As you can see, the two Epics I've created for testing exist, and are valid.

However:

This fails, and only shows "no options". This does not allow you to press enter at all, despite being a valid Epic.

Replication:

1. Create a project with a number at the end of the key
2. Create an Epic
3. Create an automation rule, any trigger
4. Add an "Edit issue" action
5. Add the "parent" field to be edited
6. Attempt to type in the Epic you created and hit enter. You are not able to. You can type in a different Epic from any project that does not have a number at the end, and hit enter. Automation will let you save this.

Workaround

You may update the field by using the "Additional fields" section on the Edit Issue component.

Below, you can find a sample JSON, for your reference:

{
    "fields": {
        "parent": {
            "key": "TEST1-1"
        }
    }
}