We can attach one or more tasks to any pull request comment, to track required work identified during a review. Anyone with permission to browse a pull request can create a task on any comment, and can browse, resolve or reopen existing tasks in the pull request.
My question is how we would know who has resolve the task or mark it as resolved ?
Hi @Vipin Chaudhary,
The best way I could find is by checking the atlassian-bitbucket-access.log.
Every time a task is updated marked as resolved or as unresolved, you'll find a line with the following content in the log:
PUT /rest/api/latest/tasks/1
The 1 here is the task id, which is an incremental number.
While this allows you to check who performed the action, it still does not tell you if the user marked the task as resolved or unresolved.
For comparison, when creating a new task, you'll see the following in the log:
POST /rest/api/latest/tasks
It would be useful if you could tell us more about why you would like to know who performed this action.
For more details on this log file, please refer to the How to read the Bitbucket Server Log Formats article.
Cheers,
Caterina - Atlassian
If there are multiple people on a team, and a task is resolved or unresolved, I want to know who marked it resolved without looking at email notifications. I'm unsure why this isn't obvious.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I completely agree.
We have some strong SDLC/Compliance requirements. We basically need 2 different reviews. A technical review - and a security review.
The pull-request can only be merged once both reviews are completed.
The proposal would be to require two reviewers - and have a task to record who did the security review.
But we cannot see who did the security review. And looking in the Bitbucket logs is not a solution.
@Caterina Curti any thoughts?
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.