I found a previous feature request that wanted to see project administrators have this specific ability. Please see https://jira.atlassian.com/browse/JRASERVER-26028 for more details.
I believe that you are seeing this because the XYZ user account does not have the Jira Administrators global permission. The project admin role is not sufficient to be able to configure this particular part. However I was able to recreate this scenario in my own test instance. I found that I did not need to have the Jira system administrator global permission to see this link. But that my example user account did have the Jira administrator global permission and I could see this "Configure Project Links" link.
I believe the problem here is in regards to the project admin role. Historically in Jira, this role has not been able to perform all administrative configurations that pertain to a single project. Many configurations such as workflow, screens, notifications, and permissions were really only able to be changed in Jira with a Jira Admin or a Jira System admin global rights.
However there is starting to be more granular differences available to this project admin role. I believe back in 7.4, project admins can now edit their own workflows (provided the workflow scheme is not shared with any other projects). I also believe that subsequent versions allow the project admin to adjust project permissions (provided the permission scheme is not shared with other projects). So there seems to be a trend to grant more and more abilities to project admins to control their own projects the way they see fit. However in this case, the application link configuration I believe still requires at least a Jira admin from the global permissions level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.