Hi All,

Great to see this feature being rolled out. We are happy to announce that Scriptrunner now supports the ability to block merges until all the comments are resolved on the pull request. You can enable this feature for a specific repository, a project, or the entire org.

More details at: https://docs.adaptavist.com/sr4bib/latest/features/script-merge-checks/built-in-merge-checks/require-all-comments-are-resolved

Scriptrunner for Bitbucket

If you click sanya khan's link, all storage media within 8 feet of your computer will be instantly erased. Then you will feel an "intense and uncontrollable feeling" that "the things ... shouldn't be happened."

The reply must be a big yes, because our  Gurgaon Call Girls has the whole fun of process from start unclothing yourself to start kissing and making an intense and uncontrollable feeling of extreme love foreplay which is like instrumental music for a singer without it you can’t even imagine a mesmerizing song and having control on your feeling and making everything step by step because most us starts slowly in the beginning but due to intense starts skipping the things that shouldn’t be happened.

The major headache for my team is that sometimes our pull requests generate hundreds of comments. The ability to sort by Unresolved comments is exactly the needed workflow. The inability means that one must manually search through active comments, outdated comments, and the Activity pane (and even then I sometimes miss a few!).

The proposed workaround of using the Tasks as a surrogate for Resolve still relies on everyone faithfully creating a Task out of any actionable comment, which introduces several points of human error. It's not practical.

This seems like such an obvious feature

These are buttons that would help a lot for everyone in my team as well... Really wish you guys could actually do it!

Simple "Resolve" and "Unresolve" actions would do it for me. Same way, as it is in the biggest competitor's platform

I find the Atlassian Bitbucket v7.6.1 interface regarding Task-Comment interactions to be simply abysmal and a huge step back in terms of usability.

Often I add a comment to a particular code change from which more than one Task could be extracted.

The new interface makes this process extremly painful and deters from giving concise review comments.

For instance, I could comment something like:

The new tool parameter option is inconsistent with the other tools and the permitted value choices are already defined in module Foo, so you should reuse instead of making your own duplicate here.

From this with previous version of Bitbucket server I would just select "parameter option is inconsistent with the other tools", then "Create Task", then select "the permitted value choices are already defined in module Foo" to create 2 tasks from this single comment.

So before the workflow was:

1. write my entire comment,
2. post
3. select piece,
4. click create task
5. select piece,
6. click create task

With the new interface, to achieve a similar effect I have to:

1. write my entire comment,
2. post
3. select relevant comment section,
4. copy,
5. add comment
6. paste
7. Create task
8. go back to original comment
9. select relevant comment section,
10. copy
11. add comment
12. paste
13. Create task

And the interface looks very ugly as now there are 3 comments one after the other for the same line.

Definitely a -1 from me.

L.E.: Another regression is that you can't easily create tasks based on other people's comments.

Scenario1:

1. Alice submits for review code
2. Bob comments that something to the effect of "if X is true, then this code should do Y"
3. Alice responds X is true in scenario S (so Y should be implemented)
4. Charlie comes to the review and sees Bob's comment then based on Bob's comment selects "this code should to Y" and Create task (blocking the merge of the faulty code and deciding not time is worth spending on the review if Y is not done)

With the new interface, Charlie would have to copy-paste Bob's comment then add his own comment to be turned into a Task.

Scenario 2:

1. Alice submits code for review
2. Bob, a new team member wonders if if X might be necessary, but is afraid to "give tasks to others" as he feels he might be wrong; alternatively says something to the effect of "I think X is also needed, what do others think?"
3. Charlie, comes and agrees X is needed, so
   1. he selects "X is needed",
   2. Create Task

With the new interface Charlie wastes more time as he needs to "click on the add comment, icon, write own text / select Bob's + copy, Create task".

joel.brostrom as of Bitbucket Server 7.0 we reworked the way tasks were implemented, this means that you can now convert a comment to a task and mark it as done to effectively make it behave as a resolvable comment.

Alternatively, as of Bitbucket Server 7.7 you can now react to comments, in my team for example some of us have taken to using the checkmark emoji to indicate that we've addressed a comment:

Regards,

John van der Loo
Developer, Bitbucket Server