We have recently started to look at integrating web hooks between our QB server instance and Bitbucket. Through some initial testing we are unable to determine how we can configure web hooks to inherit logic. When we define a web hook in a parent configuration and have Bitbucket trigger the hook on a child configuration, it returns a 400 level HTTP code. If we override the web hook at the child configuration level, the error goes away. But in doing this, we cannot maintain common logic at the parent configuration level. Our question is, is this expected behavior and by design or would you consider this a bug?
|
