The current build status API does not provide a way to link external build artifacts to commits.

The "Artifacts" column in the Builds UI is only populated through Jenkins/Bamboo Application Links, making it impossible for teams using other CI systems or external artifact storage to provide artifact links to developers.

Current Behavior:

1. The Build Status REST API (/rest/build-status/1.0/commits/{hash}{} and /rest/api/latest/projects/{projectKey}/repos/{repositorySlug}/commits/{commitId}/builds) accepts fields like state, key, name, url, and description.
2. The "Logs" and "Artifacts" columns in the Bitbucket Builds UI are only populated when using the Jenkins or Bamboo plugins with Application Links configured. These columns rely on proprietary OAuth-signed requests that cannot be replicated via standard REST API calls.
3. The description field exists in the API but is not visibly displayed in the Builds UI in Bitbucket Data Center 9.4 LTS.
4. General commit comments (created via /rest/api/latest/projects/{projectKey}/repos/{repositorySlug}/commits/{commitId}/comments) are not displayed in the UI for general comments without file anchors.

Expected Behavior:

Teams should be able to provide external artifact links that are visible to developers, regardless of which CI system they use. This could be implemented in several ways:

Option 1: Add an artifacts field to the build status API
Something like
{"state": "SUCCESSFUL","key": "build-key","name": "Build #123","url": "https://jenkins.example.com/job/123","description": "Build completed successfully","artifacts": [{"url": "https://artifacts.example.com/build/123/application.zip"{color:#abb2bf,{}}
{{     "url": "https://artifacts.example.com/build/123/test-results.xml"{color:#abb2bf}}]{color:#abb2bf}}}}
Option 2: Make the description field visible in the Builds UI

Display the description field when clicking on a build status or in a tooltip/expanded view, allowing teams to include artifact links there.