How to get back to "old theme" (prior to 5.10.0)

[nicholas_jallan]

The whole question fits in the title …

My whole team, including me, are more than disappointed by the new theme, including the over-flashing blue and the font.

How can we get back to the previous good-old-calm-readable-theme ?

[Tim Swan]

Hi @nicholas_jallan,

Thank you for raising this question and surfacing your feedback.

I'm a designer on Bitbucket Server and ADG in Server. If possible, could you please elaborate more on the color and font issues you and your team are having?

…change the colors to something less aggressive (the blue is really «eye-catching», to be pleasant), and a more readable font (as the new one seems to us bulky and less readable than the previous one) ?

I'm keen to hear if there are any particular workflows, screens, or even specific UI elements or tasks that this relates to.

Cheers,
Tim

[nicholas_jallan]

Hi @Tim Swan,

Thank you for getting involved in this conversation.

As i've wrote just above a few seconds earlier, i don't have 2 versions at the same time to explain really the differences you brought with this upgrade.

The overall feeling is that there is too much bolded font, and the font itself is harder to read than the previous one.

The blue color is really flashy and we were more happy with a slightly darker color, bringing less contrast. (Bolded) font and color are really the 2 things we'd like to revert to previous version.

Regarding all the workflow itself, it's almost perfectly matching for us, even if we would prefer to open a review directly on the diff instead of overview.

One last thing regarding the workflow, but not relevant for this topic, would be to bind (or group) pull requests having the same PR title over different repos. We have something like 30 repos and it happen often that for a new functionnalty we need to sync changes over 3 / 5 repos at the same time. (UI, backend ear client, backend ear service, rest services, camel roads, batches … ). Merge should be blocked on a PR if another PR with the same title can't be merged (for the «classical» reasons, like build fail or tasks to be done).

Hope you'll be able to introduce some tuning regarding the font and colors in a near future.

[Tim Swan]

Would you be able to let me know what OS and browsers you're running?

Thanks for the feedback! We've been working on figuring out where our color usage is effecting our users, and I'll take into account font-weights too.

[nicholas_jallan]

Hello @Felipe Kraemer, @Bryan Turner,

Thanks for your quick reply. I understand that, with time, it's required to evolve a software, including the UI.

If i'm right (and it may be obvious), bitbucket UI is a web interface using CSS. How come that it won't be possible to make an option in the admin console where we could select another CSS to change the colors to something less aggressive (the blue is really «eye-catching», to be pleasant), and a more readable font (as the new one seems to us bulky and less readable than the previous one) ? If you feel like «it's impossible», i would be glad to submit a merge request on your code if can have access to it.

We don't ask much more than tweaking font+color. We are totally ok to stick with the new layout (even if it's less efficient for us, by example not to be on the «diff view» when we enter an existing pull request, as the «overview» part is for us irrelevant).

My team was complaining a lot about making review with gitlab compared to bitbucket. With this update, all the feedback i have so far is something like :
«at least now gitlab seem to have a modern UI compared to bitbucket, as it has downgraded the user experience by far».

By experience, features are one thing, but UI make the difference in the long run to stick with a product over time or leave for an other one…

[Bryan Turner]

@nicholas_jallan,

Have you considered installing the Look and Feel plugin? It may allow you to make some "simple" customizations like adjusting the blue. For licensing and other reasons we do not accept pull requests for Bitbucket Server's own source, though I appreciate your interest.

Re: diff view vs. overview for pull requests, I'll note that that ordering is unchanged in 5.10. Bitbucket Server has always shown the overview first since we first introduced pull requests in Stash 1.3 several years ago. Bitbucket Cloud (bitbucket.org), on the other hand, does show the diff first. Perhaps you're thinking of something else?

Bryan

[nicholas_jallan]

Hello @Bryan Turner,

I tried this plugin after you suggested it. The tuning provided seems not to work properly yet with the current version and offers really little changes. It could be almost enough… but as it doesn't work yet, we're still with the «new theme» look and feel.

Regarding the diff vs overview, you're probably right. I can't tell exactly what changed with this update, but many coworkers where unable to find the diff view at the first glance. I can't really explain the diff as i don't have the 2 running versions at the same time.

Thank you for you hint… i look forward for this plugin to evolve a bit and work properly.

[Felipe Kraemer]

Hi @nicholas_jallan, 

Just to add a few more details on what @Bryan Turner mentioned just above:

Atlassian spent quite some time working on a new Atlassian Design Guidelines (ADG) in order to create an harmonious experience for our customers while using our suite of products. These new design guidelines include a new color palette, typography, new product logos, among other things that can be seen here.

The new ADG, which replaces the old one completely, is being included in the most recent versions of all Atlassian products. This means that the only way of getting back to the "old theme" is by restoring a backup and using one of the older product versions in which the old ADG version was used. The current ADG cannot be "switched" by the old one.

Regards,

Felipe

[Bryan Turner]

@nicholas_jallan,

Sorry to hear you don't like the new design. Unfortunately, there's no "old theme" option, though. There's significantly more involved in the new look than straight CSS changes, so trying to maintain both themes isn't possible.

Best regards,
Bryan Turner
Atlassian Bitbucket