Steps to reproduce:

• Create a new pipeline project with a Bitbucket SCM. When selecting the project, use a project name instead of a key
• Save configuration, and click "Browse Repository"

Expected:
The action link points to the repository, using the project key and repo name

Actual:
The project name is used instead

This is likely because when the pipeline SCM config is persisted, only the project name is provided from stapler (despite the fact the key is resolved when the project is looked up). This issue is not appearing for multibranch or freestyle jobs. When a build is triggered, the repo is initialized properly, and the issue disappears, so it's not high priority.

Workaround:
Kick off a build on the affected, either by webhook or manually.