New issues created within an Epic should pre-populate the projects dropdown

Problem

As a user creating a new issue within the context of an Epic, the expectation is that the new issue created will be linked to the epic in which it is created under. This works as expected.

But, when prompted to name the issue and assign it to a project, I have the same expectation, where I would expect the system to know the context in which I am working in and pre-populate the project field, allowing me to optionally change it if needed.

My assumption is that new issues created in the context of an epic will most commonly also be part of the same project that the epic is in.

Also, in terms of performance, searching for the current project in the dropdown takes ~12sec every time.

Pre-populating this field with a good default should increase the perception of system performance.

Current state

Proposal

• Pre-populate the "Project" dropdown with the same project that the epic is in.

MVC

Using localStorage. default it to whatever project the user used last when creating an issue from here, similar to what we do when creating an issue from the group issue list.