Issue Summary

This bug causes inline issue create to fail on the Timeline page.
It can occur in Company Managed Projects when a dropdown custom field is configured and used in multiple contexts (board, screen, project, etc. Specifically, when

• The custom field is a required field and used in the Board Filter
• The option names are not globally unique wherever that custom field is used

This can be verified by using the Configure Custom Field page and confirming if an option is used in multiple contexts.
Once on that page:

1. Search for the required custom field
2. Click the contexts tab
3. Click the "Create, edit or delete contexts" link
4. Search for the option name

An example board query that could trigger this bug is `project = xxx and "<custom field name>[Dropdown]" in (<option name>) order by Rank asc`, though only when the option name is used in multiple different contexts.

Steps to Reproduce

1. Create a dropdown custom field (single select) and associate with your project
2. Create an option under that custom field
3. Configure the custom field to add multiple contexts and create an option of the same name for each context (you need to leave the default option as "none")
4. Make the custom field a required field and make the required `description` field optional
5. Create a board which has a filter on the custom field `project = xxx and "<custom field name>[Dropdown]" in (<option name>) order by Rank asc`
6. Create a base-level issue under an epic using inline issue create (IIC)

Expected Results

It should trigger global issue create (GIC) with necessary pre-filled data for issue creation.

Actual Results

A flag pops up saying "Something went wrong, <custom field name> is required.

Workaround

Do not use  inline create on the Timeline page and use Global Issue Create instead.

There is currently no workaround to use inline create because the board JQL can only reference option names and not ids.
Options would need to be renamed until they are unique otherwise, which may affect workflows.