-
Suggestion
-
Resolution: Fixed
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 for a long time. One of the improvements is the new tasks, which can now be created without parent comment.
Please, don't hesitate to leave feedback on the feature in the comments below. We would like to know if new tasks solve your problems.
You can find more information in the Bitbucket Server 7.0 release notes and Pull Requests documentation.
Anton Genkin
Product Manager Bitbucket Server
Original description
My team loves the new tasks; they certainly make the review process much nicer!
It would be really great if you could create task items directly on the diffs without having to create a comment first. Sometimes the task is large enough to need a comment, and then break it out in to tasks. Other times it's a simple task like "Add javadocs".
There are a couple of other possibilities for this:
- Asking for changes to files that haven't been modified yet (example: "Add missing changes to ThisOtherService.java")
- Grouping together changes for multiple files (example: "Clean up the changes in the com.example.controllers package")
- duplicates
-
- Closed
-
- Closed
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-5233] Allow the creation of tasks without requiring a comment
This should be similar to the "Needs Resolution" feature in Crucible (a sister Atlassian code review product), where the comment itself may be marked as "Needs Resolution," which is essentially equivalent to pull request "tasks"
As tasks are only a workaround for comments not working correctly in the first place, I think it would be far better if comments simply always had to be addressed. For some small number of comments the person making the comment could mark it as already addressed / unimportant, but the vast majority of comments are for actual changes to be made, and it's too errorprone at the moment because when new commits come in you have no idea what has been addressed.
Any progress on this? I would even be happy with it being able to put a simple checkbox in the description of the pull request as markdown
After about 12 months, is there any hope that someone starts this task?
It's sensible that your data model requires tasks to be attached to comments. I think I would settle for an "add task" button in the comment editing toolbar, so that you can create the tasks inline with the comment. Another alternative would be a "Convert to task" button that would do the equivalent of selecting the entire comment and adding it as a task.
Thanks @Roger Barnes.
For the record, we often end up having tasks that tell the exact same thing as the comment they're attached to.
Hi gpakosz, this is something we'd like to improve someday, but due to other projects it's not on our planning radar for the next 6-12 months, I'm afraid.
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 for a long time. One of the improvements is the new tasks, which can now be created without parent comment.
Please, don't hesitate to leave feedback on the feature in the comments below. We would like to know if new tasks solve your problems.
You can find more information in the Bitbucket Server 7.0 release notes and Pull Requests documentation.
Anton Genkin
Product Manager Bitbucket Server