Kind of torn on this…
Our district’s dev team has historically used Azure DevOps to pull in their tickets from iiQ and work them via ADO - and they are also closing them that way too.
It was brought to my attention that the API suddenly will not allow them to close tickets without resolution actions.
This is where I’m torn:
The Site Option for us to require resolution actions has always been enabled, intentionally. They were really the only group not using them because they worked via API, and we just rolled with it.
Part of me wants to assume that this recent change is intended, because it should have been in line with our Site Option setting, but then part of me possibly believes it is related to this issue:
So I was questioned today - “why weren’t we notified of this change?”
My answer was a little bit of a theory on both…
It may have been a bug all along, and you were never supposed to be able to do that, or
It may be a bug now, but really you should be using resolution actions anyway - like everyone else.
I did provide them with the info/endpoint needed to add an action, and they have since “fixed” their process, but I’d like to know what everyone else is experiencing.
Anyone else resolving tickets via API in here - were you adding resolution actions already, or have you had to modify your scripts lately? Does anyone know if this was an intended change?
