Stash Repository frequently reports "Access Removed" messages when there is no issue

Summary

Due to limitations in Stash, Bamboo has to store the ssh key for a linked repository against an individual user when the repository is first created/saved. When a Bamboo user who didn't create/save the linked repo looks at it, Bamboo can't find the SSH key in their profile and will display the red banner error message below:

Click Save repository at the bottom of this screen to re-establish access to this repository.

This message is harmless. If this second user then saves the repository to get rid of the red error message, the new key will be saved against that second user and the original user will now see the red error message. Users may find themselves going round in circles (and generating an unnecessary number of keys in their Stash accounts along the way).

Steps to Reproduce

1. Connect your Bitbucket Server to your Bamboo instance using AppLinks
2. Add a "Linked Repository"
3. Connect as a second user and view this "Linked Repository" and the message will be displayed

Expected Results

The intent of this message is to show the administrator the checkout of a "Linked Repository" is failing due to a missing SSH key (i.e. the SSH key had been removed from the Stash by mistake).

Of course, with the limitation of adding the SSH key to the user who created the repo in Stash, showing the message to people who didn't save the repository does not help.

Therefore, the message should be shown only if they key was removed from the profile of the person who created the repo.

Conversely, having Bamboo using access keys as opposed to personal keys would be a better solution.

Actual Results

The red banner is shown every time.

Workaround

The repository still continues to work, doing its change detection and clones/fetches using the correct user/key combination as when another Bamboo user saves the repo, the SSH keys will be saved to his Stash account's profile. Therefore this message is harmless and more an annoyance for the Bamboo users and should be fixed.