I'm noticing in our data center installation (running 7.3.0) that the unified diffs outside of pull requests still do not have syntax highlighting. Is this on the roadmap as well?

Hi all,

I'm excited to share that in Bitbucket Server 7.0 we shipped redesigned and optimized pull request page with several improvements you’ve been asking us, including syntax highlighting in unified diffs.

You can find more information in the Bitbucket Server 7.0 release notes and Pull Requests documentation.

Please, don't hesitate to leave feedback on the feature in the comments. This will help us to priorities further development.

Anton Genkin
Product Manager Bitbucket Server

We want syntax highlights for Elixir please!!

🦄🦄🦄🦄🦄🦄🦄🦄

This basic functionality is requested since 2012, for almost 6 years now...

And this is payed product which costs $2000 for eleven users!

Atlassian, what a shame! I stumble upon such long-living annoying bugs in Confluence and Bitbucket quite often. I used to love Atlassian, but I'm starting hate...

I know I'm being provocative - but I've been going through a number of highly voted issues now that seem like must-have features for a product such as Bitbucket - especially when your biggest (free) competitor has the same functionality - and a pattern of postponing the issues or complete lack of information about what is prioritized and a roadmap for the features is very apparent.

I was honestly beginning to wonder if Bitbucket had active maintenance and roadmaps. You indicate there is - I'm still a sceptic, though.

lbig927911904,

One point of clarification re: the unicorn emoji. That was actually not even completed by a member of the Bitbucket Server team. It was implemented by a member of the support team, as a bit of fun. Aside from clicking "Approve" on the pull request, no one from Bitbucket Server was involved with that issue.

Best regards,
Bryan Turner
Atlassian Bitbucket

This is one (of many) reason why we moved from BitBucket to Gerrit, where syntax highlighting is supported out-of-the-box.

Lasse, I'm sure that a unicorn emoji doesn't require ANY development resources - they're different teams. I'm sure they're doing their best to get around to this feature, considering the priorities in the rest of their backlog. All we can do is voice our wants by a vote.

While I want to believe that you are prioritizing feature matching a superior, and free, alternative, I find this and get discouraged: 

I understand that this is not even remotely on the same order of scale to implement - but still.

That you have only within the last year enabled us to search via the full and short SHA is remarkable, that is basic functionality for a review tool. The cadence I have seen from Atlassian on fixing issues in the backlog is not encouraging.