Issue Summary

If you use the "create linked issue" option and change the destination project where that issue is to be created,  the source issue is removed from the linked issue in the create issue screen, causing inconsistent behavior between source issues. 

NOTING: The Create issue dialogue will default the project listed to the last project selected in a create screen, so if you try to create twice in a row to same project the second attempt will populate the issue in the linked issue field

you have to manually add in the issue key to get the link to be added, this additional overhead is removing the sole reason that the feature exists in the first place.

However, this does get added in automatically if you do the same from a source project type of team managed business or to a company managed business, or to a service management project, the failure to populate the field seems to be only when doing some cross-project linking but not others

Steps to Reproduce

1. create an issue in a Company-managed Software project
2. Select the "Create Linked Issue" option from the source project to trigger the create issue dialogue
3. Set the destination project in the "create issue" dialogue to a team-managed software project
4. Note the issue key is not added to the "Linked Issues" field
   

Expected Results

the source issue is listed automatically in the linked issues field

Actual Results

The field is not populated and must be manually populated, and when changing project types the value is removed from the field The following table describes the variation in behavior when selecting the "Create Linked Issue" in the different source and destination projects:

Workaround:

The only way to bypass this behavior is to manually enter the source ticket if the project type is not listed when creating a linked issue under a fail condition per the table above