Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Branch name (source -> target) in PR list gets truncated when commit message is long

sahil trambadiya
November 5, 2025

On the Pull Requests list in Bitbucket Cloud, the commit message and the branch info are shown on the same line, for example:

Refactor filter handling in WebhookErrors component to ensure proper JSON parsing... feature/abc-101 -> master

image.png

The problem is that when the commit message is long, the feature/abc-101 -> master part gets pushed behind the Created column and becomes hidden. So we can’t quickly see which branch is merging into which without opening the PR. That slows down code review because we have to click into PR details just to confirm the target branch.

Expected behavior:
The branch relationship (source -> target) should always remain fully visible in the PR list, regardless of commit message length.

 

This was previously requested here: 

https://jira.atlassian.com/browse/BCLOUD-23849

but it remains unresolved.

1 answer

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 10, 2025

Hi Sahil,

Unfortunately - there are no updates as of yet on the feature request ticket that you've referenced, and we don't have any ETA on if/when it will be implemented as such.

Feature requests are implemented based on a number of factors - you can review our policy related to this below:

I note that you are already watching that feature request and have voted for it. I'd suggest adding a comment in addition as this is accessible by our developers.

Cheers!

- Ben (Bitbucket Cloud Support)

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events