Can we change the color of the Merge button ? In the old experience, it is colored when all the policies allow a merge; in the new experience, it is back on light grey and it feels "disabled" even if it is enabled. (Huh - the button is blue on the modal dialog --- inconsistent)
I'd also like a nice green indicator instead of just text "1 of 1 passed" -- the green color allows confirmation with a quick glance or even peripheral vision without having to actually read the status.
Finally, the Approve button remains active (through also just black text on grey) after merging.
Still no task support ?
Are you planning to move on something lilke gitlab ("resolve discussion" instead of using a "task")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Alastair Wilkes .
I am also very interested on this feature. Any news about that?
Just missing that on now to get rid of Google Chrome's Refined Bitbucket extension.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can i set side by side view to default? Ignore white space is also.
Maybe you can remember my last choice?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Jon, thanks for bringing this to our attention. We’ve made a ticket in our backlog to address this, as it certainly is a feature we want to continue supporting. Thanks again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When I open an individual commit I can click an Approve/Unapprove button in the top right corner.
When I then view the PR and expand the Commits section (below comments and above the code), it shows the commits, but doesn't show the usual checkmark next to the approved commits. I use this to keep track of which commits I've looked at and which I still need to look at. Is this still supported?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I like the overview/commits tabs on the old view
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
this feature seems very interesting, is there a plan to add in Bitbucket Server?
regards,
François
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @dost , thanks for your feedback.
You should be able to switch back the old UI by enabling the 'Old pull request experience' feature on the bitbucket labs page. If you've done this and you're still seeing the new UI please raise a ticket with out support team so we can investigate further and try to fix this for you.
Isabella
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agreed, the lack of tasks is extremely frustrating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's been a year. When will this be rolled out? Please don't drag it out over two years like the 'new' issue view in Jira. It's not a good user experience getting pestered by banners asking to try the new experience for years. Some team members are still ending up in the new view while others have the old view. It's a mess.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The new PR view is really good. Much more clean and easy to use.
But we are missing task feature in the PR. Some of my colleagues are using old PR view to create task. In a new PR view I am not able to mark them after completing these task. Because of that I need to switch back again to old PR view. Can you please tell us approximately, when we expect task feature to be included in new PR view thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"likes" isn't a productivity tool; it's a social/HR tool. Why is this being prioritized above tasks and merge checklists?
I understand that some may be using it as a rudimentary acknowledgement system, but it isn't that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gotcha. One of the nice things about it was it would show real-time a number badge for new comments made by the person. If the Activity card could update real-time with added comments from other users, that would be very handy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
At this time, we don't plan to bring back that feature, but we may reconsider it in the future.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the feedback, Edward!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome. I reposted my comment there. For some reason it hadn't occurred to me the editor and the new PR experience were rather separate things. It does seem like it's currently more of a "takes some inspiration from markdown" editor. I trust they'll get it usable before rolling out the new PR experience across the board. For now I've switched both off so I can get stuff done. (I'm sure they've heard enough from me by now about the new PR experience :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The editor uses curly quotes when I type quotes characters. In probably 99% of cases, developers would want regular quotes, I'm guessing. Can that be changed? I find myself typing in quotes as part of code frequently and then a copy paste by another developer of that same bit of code is invalid (sometimes without their noticing it).
I see that regular quotes are used when the text is already identified as code (either inline with backticks or in a code block inserted with the <> icon in the editor toolbar), but usually I type the opening backtick, type some code (which ends up picking up curly quotes) and then type the final backtick which ends up turning the sequence into a monospace inline code block, but keeps the quotes curly.
Also, sometimes I'm plumb lazy and type bits of code in comments without bothering with backticks or code blocks at all. Either way, we're all coders here and probably are never going for "fancy looking text" over code.
Sorry for the bit of a rant :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recently when I go to add comments on a PR, it says "Sending" for a few seconds (which is fine). But while it's sending, it appears to block the main thread. Mouseovers, scrolling, clicking - all are suspended until it finishes saving. Can the page remain responsive while it's doing its ajax work?
As a side note, this is on a rather large-ish PR, so maybe it's not the save, per se, but a re-render of the whole page or some other overly expensive thing when only the one comment box UI needs re-rendering. Dunno.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Maxim,
We're taking a look at this. Thank you for the report.
Alastair
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A comment made on a non-changed line (e.g. a line not modified in the current code review) cannot be accessed via links in the Activity Tab.
To reproduce:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Useless without tasks...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your response and making aware about those options. Expanding and collapsing seems to be working fine.
Additionally, with longer file names we could still see that it truncates file name as per aforementioned attached picture and also suffers in loading more than 10k lines of code changes atm.
Hope these issues would be also fixed soon.
Thanks,
Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the file list on the right should scroll a little better with a long PR. oftentimes I'll see that the right list if following where I'm at but I have to scroll that side to see it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.