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
Setup a rule for all work item types and then trigger it from DevOps using a type of 'Bug' (others probably work for this as well).
Expected behavior
Rule executes and a status of 200 is returned.
Actual behavior
Rule '' failed: Input string was not in a correct format.
I've been able to look into this a little and it appears there are different 'fields' in the event from DevOps for a bug than for a Task/User Story/Feature. A mismatch of ILogger arguments seems to be the cause.
Steps to reproduce
Setup a rule for all work item types and then trigger it from DevOps using a type of 'Bug' (others probably work for this as well).
Expected behavior
Rule executes and a status of 200 is returned.
Actual behavior
Rule '' failed: Input string was not in a correct format.
I've been able to look into this a little and it appears there are different 'fields' in the event from DevOps for a bug than for a Task/User Story/Feature. A mismatch of ILogger arguments seems to be the cause.
Diagnostic logs
Event and requests
bug troubleshoot.txt
Environment
9,0 + 108PR items from SilentBob merged and deployed into Azure
The text was updated successfully, but these errors were encountered: