Jump to content

Code Review Trigger Missing Data


freaksed

Recommended Posts

I see in the docs that a mkreview trigger is supposed to include the PLASTIC_REVIEW_ASSIGNEE. But it appears that the review is being created as soon as you click create review, so it triggers before a reviewee is assigned and this field is not included.
We are using the new gui and using webhooks.

Link to comment
Share on other sites

Unfortunately, this is why the documentation describes this variable PLASTIC_REVIEW_ASSIGNEE as  "The user assigned to the code review, if any.", the scenario you mention doesn't have this variable populated, but for example, this can get populated at creation if the code review was created via the command line.

Are you able to fill your requirement with the editreview trigger instead?

Link to comment
Share on other sites

Yes I am currently using the edit review trigger to accomplish the task. I just thought it was odd that assignee is never filled because the event fires before you have a chance to assign anyone to the review. I assumed this was a bug.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...