You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Bugzilla, up to this point, we've created a new webhook per product. We have a naming convention of JBI-<environment>-<product>. For example:
Name
Product
Component
JBI-PROD-Core
Core
ANY
JBI-PROD-DataPlatformAndTools
Data Platform and Tools
ANY
JBI-PROD-DevTools
DevTools
ANY
In config, projects specify the Jira project they map to and what whiteboard tag they use. There is no information indicating which product or products a workflow uses.
This makes webhook errors hard to diagnose. For example, if I were to log in and see that the JBI-PROD-Core webhook had errors piling up and was disabled, I wouldn't have the information to know which project likely caused that blockage at a glance.
The text was updated successfully, but these errors were encountered:
In Bugzilla, up to this point, we've created a new webhook per product. We have a naming convention of
JBI-<environment>-<product>
. For example:In config, projects specify the Jira project they map to and what whiteboard tag they use. There is no information indicating which product or products a workflow uses.
This makes webhook errors hard to diagnose. For example, if I were to log in and see that the
JBI-PROD-Core
webhook had errors piling up and was disabled, I wouldn't have the information to know which project likely caused that blockage at a glance.The text was updated successfully, but these errors were encountered: