Steps to Reproduce:

• Create 2 issues and linked them together.
• Hide Linked Issues field for a field configuration scheme assigned to a project.
• Check the 2 linked issues; the Linked Issues field is still showing.
• Run a REST API to query the details of either of these issues.

https://<instance-name>.atlassian.net/rest/api/2/issue/<ticket id>

Expected Results:

Once the Linked Issues field is hidden; it should be hidden in the issue view screen. When REST API to query issue is used; it doesn't return the issueLink in the JSON response.

Actual Results:

Once the Linked Issues field is hidden; it still shows in the issue view screen but when REST API to query issue is used; it doesn't return the issueLink in the JSON response.

Workaround:

Show the Linked Issues field again and the JSON response will return the issueLink.

Notes

In my opinion; if choices are given to the user to either show or hide the Linked Issues field; the changes should be reflected in the issue view screen. Otherwise; it's better to disable users from hiding or showing the said field all together.