Task fails if "State" is not a valid choice

[robertmuehsig]

We have a pretty "old" work item template and there are "several" states, but you can't choose the state as you want, because this is "managed" by a workflow.

e.g. A "bug" is "active" then "resolved" and then "closed", but you can't change the state from "closed" to "resolved" again, because you only are allowed to go back to the "active" state.

Long story short: Some of our bugs are "closed" manually, and with your workitem update our build fails with this:

2019-02-25T12:39:17.1961692Z Found WorkItem: 13537
2019-02-25T12:39:17.1962488Z Updating WorkItem 13537
2019-02-25T12:39:17.1964322Z Patch: /fields/System.State Resolved
2019-02-25T12:39:17.1964499Z Patch: /fields/WEF_3A292E1060A74F0D855805CD82AF410E_Kanban.Column.Done false
2019-02-25T12:39:17.2710005Z ##[error]Error: The field 'State' contains the value 'Resolved' that is not in the list of supported values

It would be nice if we could somehow say that this is "ok". If the workitemupdater can't set the state to "resolve" the reason might be that the bug is already closed, which is fine for us.

Let me know if you need any other information.

Thanks for your work - we are glad that the "tag" feature is working quite well! 👍

[robertmuehsig]

Edit: I'm stupid - I guess we can just use the filter and then it should be fine. Sorry & again. Thanks for your plugin!