We have a process for handling issues where the developer moves the work item to the "Resolved" state when he thinks he has finished his work. Then it is up to the person who reported that issue to check if the resolution meets his needs and move it to the "Closed" state. However people often don't bother moving the work items to the "Closed" state, so a lot of work items are piling up in the "Resolved" state.
Is it possible to automatically move work items from one state to another after an inactivity timeout (like 1 week or so)?
There is no built-in feature in Azure DevOps to automatically move work items from one state to another after an inactivity timeout.
You could use below workaround:
Get the work items via rest api Wiql - Query By Wiql, which
changedate
before 1 week.Update the work items state to closed via rest api Work Items - Update.
my powershell script for your reference:
You can run the script on a scheduled basis, for example, use devops pipeline with schedule trigger to run every week, or other schedule trigger tool like Azure Logic Apps, it's up to you.
Edited: change to use @today-7 for System.ChangedDate value.