We dont use bitbucket tasks because we dont really understand what they are. We just jira to track tasks. Are bitbucket tasks the same as jira tasks?
What are the use cases for default tasks? When you push a PR, the only task is for other developers to review the code, which doesnt need a task as its already listed under PRs.
Are tasks a way to enforce that at least X developers have approved the PR?
Default pull request tasks are not similar to Jira tasks, they are more like tasks in Confluence. You can add them as a checklist for the pull request, and you can prevent the pull request from being merged unless all the tasks are checked off. At my previous job we used them just like that, as a checklist that had to be completed before the pull request could be merged. It was use as sort of a control that everything complied to our development process.
So maybe we can use a task to enforce that at least one developer has reviewed the PR? Or can the PR author complete the task? If so it wont help this unfortunately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anyone that have access to the PR can complete the task, and back in the days I used Bitbucket it was not possible to see who completed the task, not sure if that has changed since then...
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.