Since upgrading to JIRA 8.0.2, a custom field is automatically linking to issues in another project.

[chris martin]

Project-X  (XXPROJECT) and Project-Y (YYPROJECT)

We have a custom field in Project-X, say called CUSTOMX. Since we've upgraded to JIRA 8.0.2, this custom field is now automatically creating a link to issues in another project. 

The values stored in CUSTOMX are XX-123 or YY-123, but somehow they're linking the YY-123 value to tickets in YYPROJECT, even though issues in YYPROJECT are represented by YYPROJECT-1, YYPROJECT-2, YYPROJECT-3, etc. 

Not sure how it's linking YY-123 in a custom field from Project-X to Project-Y, when issues in Project-Y are listed as YYPROJECT-123. 

Sorry if this is confusing, it's best way I can describe it.

See example image below. Prod Key is a custom field, SSC-248 is linking to an issue in a different project where the issue number is actually SSCEEP-248.

Addons we use:

- Issue Type Filters

- Project Configurator

- Zephyr for JIRA

- JSU Automation Suite for JIRA Workflows

[Jamie Rogers]

I've seen this behaviour before with Jira - if you have text that could also be a Jira issue it will auto-create a link to it. We are running Jira 8.1 and I can replicate what you describe.

I am not sure how to disable it though - I thought maybe changing the field searcher type from free-text to none might do it but the behaviour is the same.